CVE-2025-67510: Neuron core/neuron ai Neuron MySQLWriteTool Allows Arbitrary/destructive SQL Vulnerability

CRITICAL
Advisory Identifier: GHSA-898v-775g-777c
CVSS 9.4
CWE-284 CWE-250
Published
Advisory Summary

CVE-2025-67510 is a CRITICAL (CVSS 9.4) neuron mysqlwritetool allows arbitrary/destructive sql vulnerability (CWE-284: Improper Access Control) affecting Neuron core/neuron ai libraries in the Packagist ecosystem. The issue involves neuron mysqlwritetool allows arbitrary/destructive sql when exposed to untrusted prompts (agent “footgun”). Remediation is available by upgrading affected packages to version 2.8.12.

CVE-2025-67510 at a Glance

CVE Identifier CVE-2025-67510
GHSA Identifier GHSA-898v-775g-777c
Severity CRITICAL
CVSS v3.1 Base Score 9.4
CWE Classification CWE-284: Improper Access Control
Affected Product Neuron core/neuron ai
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 9.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-67510

To remediate this vulnerability, upgrade all affected Neuron core/neuron ai dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

neuron-core/neuron-ai fixed: 2.8.12
Upgrade neuron-core/neuron-ai to 2.8.12
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for neuron-core/neuron-ai

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-67510, inspect your project dependencies for Neuron core/neuron ai:

inspect dependencies for neuron-core/neuron-ai

Analyze the terminal output to locate any version of Neuron core/neuron ai in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.8.12), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Neuron core/neuron ai, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `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). **Who is impacted:** Deployments that expose an agent with `MySQLWriteTool` enabled to untrusted input and/or run the tool with a DB user that has broad privileges. ### Patches **Not patched in:** 2.8.11 Recommended improvements (even if keeping the tool intentionally powerful): - Provide a safer API that supports only constrained operations (e.g., `insertRecord`, `updateRecord`) with allowlisted tables/columns. - Add a policy/allowlist layer (e.g., allow only `INSERT`/`UPDATE` on selected tables; forbid `DROP/TRUNCATE/ALTER/GRANT`). - Add optional review workflow: log + require human approval for high-risk statements; or “dry-run” mode. - Document strongly that the tool must not be exposed to untrusted prompts without additional safeguards. ### Workarounds - Do not enable `MySQLWriteTool` for public/untrusted agents. - Use a dedicated DB user with **least privilege**: - no `DROP`, no `ALTER`, no `GRANT`, no access to sensitive tables unless necessary - Add an application-layer policy rejecting high-risk statements (`DROP`, `TRUNCATE`, `ALTER`, `GRANT`, `REVOKE`, `CREATE USER`, etc.). - Implement authorization gating for tool calls (RBAC, allow tool use only for trusted operators).

CVE-2025-67510 Affected Neuron core/neuron ai Versions

1 component(s)
Fixed Versions:
2.8.12
Product / Package Ecosystem Affected Versions Fixed Version
neuron-core/neuron-ai
Packagist
< 2.8.12
2.8.12

References

Frequently Asked Questions

What is CVE-2025-67510?
CVE-2025-67510 is a security vulnerability in Neuron core/neuron ai involving Neuron MySQLWriteTool allows arbitrary/destructive SQL when exposed to untrusted prompts (agent “footgun”) under CWE-284: Improper Access Control.
Which Neuron core/neuron ai versions are affected?
Affected versions include releases prior to 2.8.12 across affected packages: neuron-core/neuron-ai.
What version fixes CVE-2025-67510?
Upgrading to 2.8.12 (or the latest patched release for your respective branch) resolves the vulnerability.
Is neuron-core/neuron-ai affected?
Yes, neuron-core/neuron-ai is affected in releases prior to 2.8.12. Upgrade your dependency to 2.8.12 or later.
What is the CVSS score of CVE-2025-67510?
CVE-2025-67510 has a CVSS v3.1 base score of 9.4 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H.
What CWE is associated with CVE-2025-67510?
CVE-2025-67510 is classified under CWE-284: Improper Access Control (The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.).
How can I check Packagist dependencies for CVE-2025-67510?
Run the dependency tree command: 'inspect dependencies for neuron-core/neuron-ai'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-898v-775g-777c",
  "modified" : "2025-12-11T15:49:17Z",
  "published" : "2025-12-09T17:19:42Z",
  "aliases" : [ "CVE-2025-67510" ],
  "summary" : "Neuron MySQLWriteTool allows arbitrary/destructive SQL when exposed to untrusted prompts (agent “footgun”)",
  "details" : "### Impact\n\n`MySQLWriteTool` executes arbitrary SQL provided by the caller using `PDO::prepare()` + `execute()` without semantic restrictions.  \n\nThis 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).\n\n\n\n**Who is impacted:** Deployments that expose an agent with `MySQLWriteTool` enabled to untrusted input and/or run the tool with a DB user that has broad privileges.\n\n### Patches\n\n**Not patched in:** 2.8.11  \n\nRecommended improvements (even if keeping the tool intentionally powerful):\n\n- Provide a safer API that supports only constrained operations (e.g., `insertRecord`, `updateRecord`) with allowlisted tables/columns.\n\n- Add a policy/allowlist layer (e.g., allow only `INSERT`/`UPDATE` on selected tables; forbid `DROP/TRUNCATE/ALTER/GRANT`).\n\n- Add optional review workflow: log + require human approval for high-risk statements; or “dry-run” mode.\n\n- Document strongly that the tool must not be exposed to untrusted prompts without additional safeguards.\n\n\n\n### Workarounds\n\n- Do not enable `MySQLWriteTool` for public/untrusted agents.\n\n- Use a dedicated DB user with **least privilege**:\n\n  - no `DROP`, no `ALTER`, no `GRANT`, no access to sensitive tables unless necessary\n\n- Add an application-layer policy rejecting high-risk statements (`DROP`, `TRUNCATE`, `ALTER`, `GRANT`, `REVOKE`, `CREATE USER`, etc.).\n\n- Implement authorization gating for tool calls (RBAC, allow tool use only for trusted operators).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "neuron-core/neuron-ai"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.8.12"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.8.11"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/neuron-core/neuron-ai/security/advisories/GHSA-898v-775g-777c"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-67510"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/neuron-core/neuron-ai/commit/44bab85d92bf162898ee48d0bcef6ba0d29b59c9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/neuron-core/neuron-ai"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/neuron-core/neuron-ai/releases/tag/2.8.12"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-250", "CWE-284" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-09T17:19:42Z",
    "nvd_published_at" : "2025-12-10T23:15:48Z"
  }
}