# CVE-2025-15396: Library Viewer < 3.2.0 - Reflected Cross-Site Scripting

> Reflected XSS in Library Viewer plugin allows attackers to execute scripts against admins, potentially leading to account takeover.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Feb 2026
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-94gf-82q2-rv5g

## What is CVE-2025-15396?

CVE-2025-15396 is a high-severity cross-site scripting vulnerability in Unknown Library Viewer, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Library Viewer WordPress plugin before 3.2.0 does not sanitise and escape some parameters before outputting them back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

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

## Which versions are affected by CVE-2025-15396?


## How do I fix CVE-2025-15396?

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

## Is CVE-2025-15396 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15396 and fix it if it is affected.

What it is: CVE-2025-15396 is a high-severity cross-site scripting vulnerability in Unknown Library Viewer, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15396 exists.

Affected product: Unknown Library Viewer. 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-2025-15396/ (Markdown: https://insights.sbomify.com/CVE-2025-15396/index.md)
```

## Sources

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

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