{"answers":{"affected":"2 open source packages ship an affected version, including neuron-core/neuron-ai. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-67509 in the wild and no public exploit code.","fix":"Upgrade neuron-core/neuron-ai to 2.8.12 or later.","what":"CVE-2025-67509 is a high-severity code injection vulnerability in neuron-core neuron-ai, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-67509 and fix it if it is affected.\n\nWhat it is: CVE-2025-67509 is a high-severity code injection vulnerability in neuron-core neuron-ai, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-67509 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- neuron-core/neuron-ai (Packagist): affected all versions; fixed in 2.8.12\n- neuron-core/neuron-ai (Packagist): affected all versions; fixed in 2.8.12\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-67509/ (Markdown: https://insights.sbomify.com/CVE-2025-67509/index.md)","id":"CVE-2025-67509","markdown":"https://insights.sbomify.com/CVE-2025-67509/index.md","name":"CVE-2025-67509","record":{"aliases":["GHSA-j8g6-5gqc-mq36"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"PHP AI agent framework","requires_auth":"none","summary":"Attackers can bypass read-only SQL restrictions to write arbitrary files on the server via prompt injection, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"neuron","vendor":"neuron-ai"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass.  MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"MySQLSelectTool Read-Only Bypass via SELECT INTO OUTFILE Allows Arbitrary File Write","id":"CVE-2025-67509","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"MySQLWriteTool allows arbitrary/destructive SQL when exposed to untrusted prompts (agent “footgun”)","id":"CVE-2025-67510"},"packages":[{"ecosystem":"Packagist","fixed":["2.8.12"],"introduced":["0"],"last_affected":[],"package":"neuron-core/neuron-ai","purl":null,"source":"GHSA-j8g6-5gqc-mq36"},{"ecosystem":"Packagist","fixed":["2.8.12"],"introduced":["0"],"last_affected":[],"package":"neuron-core/neuron-ai","purl":"pkg:composer/neuron-core/neuron-ai","source":"GHSA-j8g6-5gqc-mq36"}],"prev":{"headline":"gardenctl is vulnerable to Command Injection when used with non‑POSIX shells","id":"CVE-2025-67508"},"products":["neuron-ai"],"published":"2025-12-10","related":[{"cvss_score":9.4,"headline":"MySQLWriteTool allows arbitrary/destructive SQL when exposed to untrusted prompts (agent “footgun”)","id":"CVE-2025-67510","kev_date_added":null,"published":"2025-12-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-11","vendors":["neuron-core"]},"summary":"Attackers can bypass read-only SQL restrictions to write arbitrary files on the server via prompt injection, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2025-67509/"}