CVE-2025-67510: Neuron-ai Neuron privilege escalation (CVSS 9.4)

Description

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityLow

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H

Affected products

Neuron-ai Neuron< 2.8.12

Remediation

Fixed in

Neuron-ai Neuron≥ 2.8.12

Patch & vendor advisories

References

https://github.com/neuron-core/neuron-ai/commit/44bab85d92bf162898ee48d0bcef6ba0d29b59c9Patch
https://github.com/neuron-core/neuron-ai/releases/tag/2.8.12ProductRelease Notes
https://github.com/neuron-core/neuron-ai/security/advisories/GHSA-898v-775g-777cMitigationVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-67510 being actively exploited?

CVE-2025-67510 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.41%.

How severe is CVE-2025-67510?

CVE-2025-67510 has a CVSS 3.1 base score of 9.4, rated critical. EPSS estimates a 0.41% probability of exploitation.

Which products are affected by CVE-2025-67510?

Affected products include Neuron-ai Neuron.

How do I fix CVE-2025-67510?

Upgrade affected software to a fixed version, for example Neuron-ai Neuron 2.8.12 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-67510 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo