# CVE-2026-130375: AdminNeo before 5.9.1 RCE via SQLite file: URI database name


- **Severity:** High 8.6 (`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 in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-xfph-wm76-882f, UBUNTU-CVE-2026-130375

## What is CVE-2026-130375?

CVE-2026-130375 is a high-severity vulnerability in adminneo-org AdminNeo, published on 17 Nov 2026. 

### Official 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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-130375?

1 open source package ship an affected version, including adminneo-org/adminneo.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `adminneo-org/adminneo` | Packagist | `pkg:composer/adminneo-org/adminneo` | All versions | 5.9.1 |

## How do I fix CVE-2026-130375?

Upgrade adminneo-org/adminneo to 5.9.1 or later.

## Is CVE-2026-130375 being exploited?

There is no known exploitation of CVE-2026-130375 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130375 and fix it if it is affected.

What it is: CVE-2026-130375 is a high-severity vulnerability in adminneo-org AdminNeo, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130375 in the wild and no public exploit code.

Affected packages and fixed versions:
- adminneo-org/adminneo (Packagist): affected all versions; fixed in 5.9.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130375/ (Markdown: https://insights.sbomify.com/CVE-2026-130375/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130375
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130375
- OSV: https://osv.dev/vulnerability/CVE-2026-130375

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130375/
Summaries are generated and may contain mistakes; the official description above is the record.
