CVE-2026-130375
7.2HighPublished 17 Nov 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-434
What an attacker gets
Authenticated attackers with SQLite access can achieve remote code execution by writing PHP files to the webroot. This requires an existing administrative account.
Root cause
The application fails to properly sanitize SQLite database names, allowing attackers to use PDO_SQLite file: URI schemes to write arbitrary files.
Affected versions
AdminNeo before 5.9.1
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade to AdminNeo 5.9.1 or later. If you cannot patch immediately, restrict database configuration access to trusted administrators and ensure the web server user lacks write permissions to the webroot.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.
References
- https://github.com/adminneo-org/adminneo/releases/tag/v5.9.1
- https://github.com/adminneo-org/adminneo/security/advisories/GHSA-2gwx-67mg-hfr3
- https://github.com/adminneo-org/adminneo/security/advisories/GHSA-r6xv-mvwg-hfrw
- https://www.vulncheck.com/advisories/adminneo-before-5.9.1-rce-via-sqlite-file-uri-database-name