CVE-2026-122059 · Package
NO FIX YET
The WP ImageViewer plugin for WordPress does not sanitize the img.alt attribute, so stored script code runs in pages. An authenticated attacker with subscriber-level access or higher can inject a payload that runs in the browser of any visitor who opens the injected page.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the WP ImageViewer plugin at version 3.0.2 or lower. Exposure is higher where a front-end content plugin such as bbPress is active, which lets Subscriber-level users publish image content, or where Contributors can submit image HTML in posts (the WordPress default). On a default installation without those settings, an attacker needs custom-level access or higher.
Not affected if no-untrusted-user-accounts, plugin-not-installed, plugin-version-above-3.0.2
Who cares bbpress, wordpress, wp-imageviewer
3.0.2 or lower.No fix yet, per the sources.
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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.