# CVE-2026-27973: Audiobookshelf has Stored XSS in ItemSearchCard.vue via Audiobook Metadata (Search Results on Mobile App)

> Attackers with library modification privileges can execute arbitrary JavaScript in the Audiobookshelf mobile app via malicious metadata, leading to session hijacking and data exfiltration.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-2433-p93m-xhhg

## What is CVE-2026-27973?

CVE-2026-27973 is a medium-severity cross-site scripting vulnerability in advplyr audiobookshelf, published on 26 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Audiobookshelf is a self-hosted audiobook and podcast server. A stored cross-site scripting (XSS) vulnerability exists in versions prior to 0.12.0-beta of the Audiobookshelf mobile application that allows arbitrary JavaScript execution through malicious library metadata. Attackers with library modification privileges can execute code in victim users' browsers/WebViews, potentially leading to session hijacking, data exfiltration, and unauthorized access to native device APIs. The issue is fixed in audiobookshelf-app version 0.12.0-beta, corresponding to audiobookshelf version 2.12.0.

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

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

It affects 2 products.


Products: Audiobookshelf Audiobookshelf, Audiobookshelf Audiobookshelf Mobile App.

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

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

## Is CVE-2026-27973 being exploited?

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

## Other vulnerabilities in advplyr audiobookshelf

- [CVE-2025-57800](https://insights.sbomify.com/CVE-2025-57800/): Audiobookshelf vulnerable to OIDC token exfiltration and account takeover (high 8.8)
- [CVE-2025-25205](https://insights.sbomify.com/CVE-2025-25205/): Remote Authentication-Bypass can lead to server crash or limited information disclosure due to faulty pattern matching (high 8.2)
- [CVE-2023-47619](https://insights.sbomify.com/CVE-2023-47619/): Audiobookshelf Server-Side Request Forgery and Arbitrary File Read Vulnerability (high 8.1)
- [CVE-2023-47624](https://insights.sbomify.com/CVE-2023-47624/): Audiobookshelf Arbitrary File Read Vulnerability (high 7.5)
- [CVE-2025-46338](https://insights.sbomify.com/CVE-2025-46338/): Audiobookshelf Vulnerable to Cross-Site-Scripting Reflected via POST Request in /api/upload (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27973 is a medium-severity cross-site scripting vulnerability in advplyr audiobookshelf, published on 26 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-27973 in the wild and no public exploit code.

Affected product: advplyr audiobookshelf. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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