CVE-2026-130375

AdminNeo before 5.9.1 RCE via SQLite file: URI database name

Published Nov 17, 2026 CVSS 4.0 · 8.6 High EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

AdminNeo before version 5.9.1 includes a remote code execution flaw that allows authenticated users of its SQLite component to bypass the check_sqlite_name guard using PDO_SQLite file: URI database names. By selecting the PDO driver with ext=pdo and submitting database names such as file:/webroot/x.php?x=.db, an attacker can cause the system to create a .php file in the webroot. The attacker can then store PHP source code in table data, which is later executed by the web server. This vulnerability directly leads to arbitrary code execution on the host with the privileges of the application process.

Affected Systems

AdminNeo software versions earlier than 5.9.1. Specifically any release of AdminNeo before 5.9.1, distributed by the adminneo-org organization. The flaw exists in the SQLite handling code of these releases.

Risk and Exploitability

The CVSS score of 8.6 classifies this as high severity. The EPSS score is not available, so current exploitation probability cannot be quantified, but the flaw is not listed in the CISA KEV catalog. The attack requires an authenticated SQLite user and the ability to specify a PDO_SQLite file: URI database name. Once that condition is met, the attacker can craft a request that results in PHP code execution. The impact is full system compromise if the application runs under an account with filesystem write access and a PHP interpreter. Because the flaw can be triggered by normal application functionality, exploitation risk is high for systems that have exposed authenticated SQLite access.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade AdminNeo to version 5.9.1 or later to apply the database name validation fix.
  • If an upgrade is not possible immediately, disable the PDO_SQLite driver or block "ext=pdo" file: URI database names for authenticated users.
  • Restrict the creation of PHP files and the storage of PHP code in database tables by enforcing file type validation and removing the ability to store executable content.

Generated by OpenCVE AI on November 17, 2026 at 02:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Adminneo-org
Adminneo-org adminneo
Vendors & Products Adminneo-org
Adminneo-org adminneo
Type Values Removed Values Added
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.
Title AdminNeo before 5.9.1 RCE via SQLite file: URI database name
Weaknesses CWE-434
References
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.6, 'vector': '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'}

Weaknesses
  • CWE-434

    Unrestricted Upload of File with Dangerous Type

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 17, 2026, 1:40 AM
Reserved
Nov 17, 2026, 1:06 AM
Status
Deferred
Published
Nov 17, 2026, 2:17 AM
Modified
Nov 17, 2026, 2:17 AM