# CVE-2026-130359: AdminNeo before 5.9.1 Stored XSS via SlugifyEditPlugin Column Name


- **Severity:** Low 2.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:N/VA:N/SC:L/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-822w-w57h-m2xh, GHSA-cwvq-x3wg-574h, UBUNTU-CVE-2026-130359

## What is CVE-2026-130359?

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

### Official description

AdminNeo before 5.9.1 contains a stored cross-site scripting vulnerability in SlugifyEditPlugin::getFieldInput() that embeds column names unescaped in an inline initSlugField() call. Attackers with DDL privileges can create a slug column whose name contains a single quote, injecting JavaScript that runs under the page's CSP nonce when victims open the table's edit form.

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

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

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

Upgrade adminneo-org/adminneo to 5.9.1 or later.

## Is CVE-2026-130359 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130359 is a low-severity vulnerability in adminneo-org AdminNeo, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130359 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-130359/ (Markdown: https://insights.sbomify.com/CVE-2026-130359/index.md)
```

## Sources

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

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