# CVE-2026-122059: WP ImageViewer <= 3.0.2 - Authenticated (Subscriber+) Stored DOM-Based Cross-Site Scripting via Image 'alt' Attribute


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-jh9g-mj9g-p654

## What is CVE-2026-122059?

CVE-2026-122059 is a medium-severity vulnerability in mpol WP ImageViewer, published on 7 Nov 2026. 

### Official description

The WP ImageViewer plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'img.alt' parameter in all versions up to, and including, 3.0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires a front-end content plugin such as bbPress to be active, as it grants Subscriber-level users the bbp_participant capability needed to publish image-bearing content containing the encoded payload. Exploitation by attackers with contributor-level access and above requires that the site allows Contributors (or higher) to submit image HTML in post content — the WordPress default. On a default installation, where that is not configured, the vulnerability requires attackers with custom-level access and above.

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

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


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

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

## Is CVE-2026-122059 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122059 is a medium-severity vulnerability in mpol WP ImageViewer, published on 7 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122059 in the wild and no public exploit code.

Affected product: mpol WP ImageViewer. 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-122059/ (Markdown: https://insights.sbomify.com/CVE-2026-122059/index.md)
```

## Sources

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

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