# CVE-2026-130854: AudioBookRequest 1.9.0 through 2.0.1 Stored XSS via Manual Request Fields


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-58ff-4hwj-c6vr

## What is CVE-2026-130854?

CVE-2026-130854 is a medium-severity vulnerability in markbeep AudioBookRequest, published on 17 Nov 2026. 

### Official description

AudioBookRequest 1.9.0 through 2.0.1 contains a stored cross-site scripting vulnerability that allows low-privileged authenticated users to inject script through manual book request fields due to disabled Jinja2 autoescaping. Attackers can submit malicious title, author, narrator or info values via POST /api/requests/manual to execute script in an administrator's browser and access admin-only endpoints.

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

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

1 open source package ship an affected version, including markbeep/audiobookrequest.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `markbeep/audiobookrequest` | GitHub | `pkg:github/markbeep/audiobookrequest` | From 1.9.0 to 2.0.1 | None |

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

No fix has been published for CVE-2026-130854 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130854 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130854 is a medium-severity vulnerability in markbeep AudioBookRequest, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130854 in the wild and no public exploit code.

Affected packages and fixed versions:
- markbeep/audiobookrequest (GitHub): affected from 1.9.0 up to 2.0.1; no fix listed

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

## Sources

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

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