CVE
adminneo-org/adminneo remote code execution in SQLite database name check
Affects AdminNeo before 5.9.1 on PHP servers with pdo_sqlite loaded, where a user logged in to the SQLite driver can reach the vulnerable path. Fixed in 5.9.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 5.9.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. PHP has the pdo_sqlite extension loaded, which is the PHP default Attacker is logged in to the AdminNeo SQLite driver A writable directory served by the web server
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
AdminNeo before 5.9.1 contains a remote code execution vulnerability that allows authenticated SQLite users to bypass the check_sqlite_name() extension guard using PDO_SQLite file: URI database names. Attackers can select the PDO driver with ext=pdo and submit names like file:/webroot/x.php?x=.db to create a .php file, then store PHP source as table data for code execution.
Who should check
Anyone running AdminNeo before 5.9.1 with the SQLite driver enabled, on PHP servers with pdo_sqlite loaded and a writable web-served directory.
“AdminNeo before 5.9.1 contains a remote code execution vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Packagist packages
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 34 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
PHP has the pdo_sqlite extension loaded, which is the PHP default Attacker is logged in to the AdminNeo SQLite driver A writable directory served by the web serverUpgrade to a fixed version: 5.9.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130375 (AdminNeo before 5.9.1 RCE via SQLite file: URI database name), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130375 (entry last updated 2026-11-17):
Affected:
- Packagist package adminneo-org/adminneo: fixed in 5.9.1
Fixed versions: 5.9.1.
Conditions (all must be true for the bug to be hit):
- PHP has the pdo_sqlite extension loaded, which is the PHP default (source: https://github.com/adminneo-org/adminneo/security/advisories/GHSA-r6xv-mvwg-hfrw)
- Attacker is logged in to the AdminNeo SQLite driver (source: https://github.com/adminneo-org/adminneo/security/advisories/GHSA-2gwx-67mg-hfr3)
- A writable directory served by the web server (source: https://github.com/adminneo-org/adminneo/security/advisories/GHSA-r6xv-mvwg-hfrw)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-130375 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130375 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/adminneo-org/adminneo/security/advisories/GHSA-r6xv-mvwg-hfrw
- https://github.com/adminneo-org/adminneo/security/advisories/GHSA-2gwx-67mg-hfr3
- https://github.com/adminneo-org/adminneo/releases/tag/v5.9.1
- https://www.vulncheck.com/advisories/adminneo-before-5.9.1-rce-via-sqlite-file-uri-database-name
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130375
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130375"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- adminneo-org/adminneoPackagist
fixed in 5.9.1
Evidence 6
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130375
Is CVE-2026-130375 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted SQLite file: URI used as the database name reaches a vulnerable PDO path in AdminNeo. The facts describe escalation to remote code execution as the web-server user by writing a PHP file into a web-served directory and storing PHP source in it as table data.Source: github.com, github.com, vulncheck.com
Which versions are affected by CVE-2026-130375?
adminneo-org/adminneo (Packagist): before 5.9.1.Source: cve.now feed data
Am I affected, and how do I check?
AdminNeo versions before 5.9.1 are in the affected range. The setup also needs PHP with the pdo_sqlite extension loaded (the PHP default), a user logged in to the AdminNeo SQLite driver, and a writable directory served by the web server. To check, look at the installed AdminNeo version and at whether pdo_sqlite is listed in the PHP module list (for example, the output of php -m).Source: github.com, github.com, vulncheck.com
How do I fix CVE-2026-130375?
Upgrade AdminNeo to 5.9.1 or later, which is the listed fixed version. The sources name no patch identifiers or workaround.Source: github.com, github.com, vulncheck.com