# CVE-2026-130364: AdminNeo before 5.9.1 Reflected HTML Injection via where Parameter Keys


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-h6gv-2whh-8c86, GHSA-v6vc-7g4r-9369, UBUNTU-CVE-2026-130364

## What is CVE-2026-130364?

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

### Official description

AdminNeo before 5.9.1 contains a reflected HTML injection vulnerability that allows remote attackers to inject markup by supplying crafted array keys in the where URL parameter. Attackers can trick logged-in users into opening a link whose unescaped keys land in select search form name attributes, enabling meta refresh redirects and content spoofing.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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

Upgrade adminneo-org/adminneo to 5.9.1 or later.

## Is CVE-2026-130364 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130364 is a low-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-130364 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-130364/ (Markdown: https://insights.sbomify.com/CVE-2026-130364/index.md)
```

## Sources

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

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