Skip to main content

Neuron AI CVE-2025-67509

HIGH
Code Injection (CWE-94)
2025-12-10 security-advisories@github.com
8.2
CVSS 3.1 · Vendor: github
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach public agent endpoint
  2. Delivery
    Prompt-inject SELECT ... INTO OUTFILE
  3. Exploit
    Bypass read-only keyword filter
  4. Execution
    Write PHP web shell to web dir
  5. Impact
    Execute shell for RCE

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a deployment that exposes an AI agent using Neuron's MySQLSelectTool to untrusted/attacker-influenced input (e.g., a public agent endpoint susceptible to prompt injection). The arbitrary-file-write-to-RCE outcome additionally requires that the MySQL/MariaDB account used by the tool holds the FILE privilege AND that server configuration (secure_file_priv) permits writes to a useful, ideally web-accessible, directory. Limiting factors: without the FILE privilege or with a restrictive secure_file_priv, the impact is contained to the read-only-filter bypass rather than code execution; exploitation depends on the specific agent being reachable and wired to this tool. Affected versions are 2.8.11 and below; fixed in 2.8.12.

Impact

This is a moderate-priority issue whose real-world risk is heavily gated by server-side configuration despite the 8.2 'High' base score. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N) treats it as remotely reachable without authentication (PR:N), consistent with the described attack surface: a public agent endpoint influenced via prompt injection. However, the described escalation from arbitrary file write to RCE is NOT unconditional - it requires the MySQL/MariaDB account to hold the FILE privilege AND the server's secure_file_priv/config to permit writes to a useful (e.g., web-accessible) directory. These are non-attacker-controlled preconditions, so the AC:L in the input arguably understates real-world complexity. Exploitation signals are low: EPSS is 0.29% (19th percentile), there is no CISA KEV listing, and no public exploit was provided in the intelligence - so this is 'no public exploit identified at time of analysis,' not active exploitation. No SSVC decision data was supplied. Net: a genuine and clever read-only-bypass flaw with a credible path to code execution, but the combination of niche product footprint, dependence on overly-permissive DB privileges, and absence of exploitation evidence places it below internet-facing mass-exploitation threats. Prioritize where a Neuron agent using MySQLSelectTool is exposed to untrusted input and the DB account has FILE privilege.

Exploit ScenarioDerived

An attacker sends crafted natural-language input to a publicly exposed AI agent that uses Neuron's MySQLSelectTool, using prompt injection to make the agent issue a query like 'SELECT ... INTO OUTFILE'/'INTO DUMPFILE' that bypasses the first-keyword and forbidden-keyword validation. If the DB account has the FILE privilege and secure_file_priv permits writing to a web-accessible directory, the attacker writes a PHP web shell and achieves remote code execution on the application host. No public exploit code was identified in the provided intelligence, though the GHSA advisory documents the technique in detail.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 25, 2026

Neuron AI's MySQLSelectTool (versions 2.8.11 and below) is intended to be a read-only SQL interface for LLM agents, but its keyword-based validation can be bypassed so that unauthenticated remote attackers who influence tool input - typically via prompt injection through a public agent endpoint - smuggle INTO OUTFILE/INTO DUMPFILE clauses and write arbitrary files on the database server. If the MySQL/MariaDB account used by the tool holds the FILE privilege and secure_file_priv permits writing to a web-accessible directory, this file-write primitive can escalate to remote code execution on the application host (for example, by dropping a PHP web shell). No public exploit code has been identified at time of analysis; EPSS is low at 0.29% (19th percentile), the issue is not in CISA KEV, and the vendor has released a fix in version 2.8.12 - our assessment rates real-world risk as moderate-priority because the RCE outcome is heavily gated by server-side privileges and configuration.

RemediationAI

Vendor-released patch: upgrade to Neuron AI 2.8.12, which contains commit 72735d0ea133266cf2f5d5d195d41e9dd865289a and is published at the 2.8.12 release tag; the GitHub security advisory is https://github.com/neuron-core/neuron-ai/security/advisories/GHSA-j8g6-5gqc-mq36. If upgrading immediately is not possible, apply the advisory's workarounds with their trade-offs in mind: remove or disable MySQLSelectTool entirely for any agent reachable from untrusted input (this breaks agent SQL-querying functionality but eliminates the attack surface), revoke the FILE privilege from the MySQL/MariaDB account used by the tool (defense-in-depth that does not fix the filter bypass but removes the file-write and RCE escalation path), and set secure_file_priv to a directory that is not web-accessible or restrict it tightly (server-wide change that may break legitimate import/export workloads). Additionally, layer an application-side filter that rejects INTO OUTFILE, INTO DUMPFILE, LOAD_FILE, ; multi-statements, and suspicious comment patterns, and treat this as a stopgap - the advisory recommends AST-based (SQL parser) validation over keyword checks because blocklists are bypassable.

Affected Packages

composer neuron-core/neuron-ai fix: 2.8.12

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in composer

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Neuron (packaged as composer/neuron-core/neuron-ai) is a PHP framework for building and orchestrating AI agents, and MySQLSelectTool is a built-in toolkit member that lets an agent issue SQL against a MySQL/MariaDB backend under a supposed read-only contract. The root cause is CWE-94 (Improper Control of Generation of Code / Code Injection): validation relies on checking the first keyword (e.g., SELECT) plus a forbidden-keyword blocklist, an approach that fails to account for valid SQL grammar constructs appended to a SELECT statement. MySQL and MariaDB support SELECT ... INTO OUTFILE 'path' and SELECT ... INTO DUMPFILE 'path', which write query output to a file on the database server; when the connected account has the FILE privilege and secure_file_priv allows the target path, an attacker-supplied query can create files with attacker-controlled content anywhere permitted by that setting. The vendor's fix direction is to reject file/IO constructs and move toward AST-based (parsed-statement) validation with allow-listed tables/columns and multi-statement prevention, since string/keyword matching is inherently fragile. The affected product is captured by CPE cpe:2.3:a:neuron-ai:neuron:*:*:*:*:*:*:*:*.

Know when Neuron gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 8.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
vuln.today AI 6.5 MEDIUM

Remotely reachable via public agent endpoint (AV:N, PR:N), but full impact depends on DB FILE privilege and permissive secure_file_priv outside attacker control (AC:H); arbitrary file write gives I:H, LOAD_FILE read gives C:L, no availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (github).

CVSS VectorVendor: github

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Neuron AI's MySQLSelectTool, used by LLM agents for database queries in versions 2.8.11 and below, can be abused to write arbitrary files on the database server and potentially achieve remote code execution on the application host. This puts organizations with public-facing agent endpoints at risk of server compromise, data exposure, and service disruption if the underlying database account has excessive privileges. The vendor has released a fix in 2.8.12; no public exploit has been identified at time of analysis, but the high severity and potential for code execution warrant prompt remediation.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Low
niche, recently-emerged open-source PHP AI-agent framework
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Affected Products (CPE)CVE.org

cpe:2.3:a:neuron-ai:neuron:*:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy