# CVE-2026-130374: AdminNeo before 5.9.1 SQL Injection via IN and NOT IN Search Values


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/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:** 18 Nov 2026
- **Also known as:** GHSA-c8p2-7c53-5ww9, GHSA-r6wc-chqc-5wq3, UBUNTU-CVE-2026-130374

## What is CVE-2026-130374?

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

### Official description

AdminNeo before 5.9.1 contains an sql injection vulnerability that allows remote attackers to inject SQL by supplying crafted IN and NOT IN search values that process_length() passes unescaped. Attackers can send a logged-in user a cross-site GET link using a backslash-escaped apostrophe to run blind SQL with that user's database rights on PostgreSQL, SQLite, MS SQL, Oracle, or MySQL in NO_BACKSLASH_ESCAPES mode.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

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-130374?

Upgrade adminneo-org/adminneo to 5.9.1 or later.

## Is CVE-2026-130374 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130374 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130374 is a high-severity vulnerability in adminneo-org AdminNeo, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130374 exists.

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-130374/ (Markdown: https://insights.sbomify.com/CVE-2026-130374/index.md)
```

## Sources

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

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