CVE-2026-130375 · Package
NO FIX YET · SEE WHAT TO DO
AdminNeo before 5.9.1 lets an authenticated SQLite user bypass the extension check by using PDO SQLite file: URI database names. The attacker can write a PHP file into the web root and store PHP source as table data, which then runs on the server.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
AdminNeo installations before 5.9.1 that expose SQLite databases through the PDO driver to users with login access. Teams that do not run AdminNeo, or that use other database drivers only, can skip it. Exposure depends on who holds an account that can reach SQLite connections.
Not affected if adminneo-5.9.1-or-later, auth-required, no-sqlite-connections
Who cares adminneo, php, self-hosted, sqlite
5.9.1 are affected.ext=pdo in the AdminNeo deployment.5.9.1 or later.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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.