FOOBOX-IMAGE-LIGHTBOX · CVE-2026-120687 · Other
FIX → 2.8.8 ✓ verified
The FooBox Lightbox & Modal Popup WordPress plugin, up to and including 2.8.7, does not sanitize or escape an image alt attribute inside the .wp-caption container. An attacker can store a script that runs in the browser of any visitor who opens the injected page.
first public Nov 14, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Any WordPress site running the FooBox Lightbox & Modal Popup plugin (foobox-image-lightbox) at 2.8.7 or earlier. Wordfence's description says an attacker needs Contributor access on a default install, or Subscriber access when bbPress 2.6.20 is installed with a public forum. Its title and CVSS vector (PR:N) say unauthenticated, which the description does not support. Sites without FooBox, or on 2.8.8 or later, can skip it.
Not affected if newer-version, plugin-not-installed
Who cares bbpress, foobox, wordpress, wordpress-plugin, xss
2.8.7 are affected; 2.8.8+ is fixedUpgrade to 2.8.8
Update FooBox (foobox-image-lightbox) to 2.8.8 or later; released 7 Nov 2026 per the vendor changelog (Patchstack lists as the patched version).
The Lightbox & Modal Popup WordPress Plugin – FooBox plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'img alt attribute inside .wp-caption container' parameter in all versions up to, and including, 2.8.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by Subscriber-level users when bbPress is installed, as its bbp_filter_kses filter chain permits img and pre tags while preserving numeric character references inside attribute values, allowing encoded payloads to bypass save-time sanitization and reach the vulnerable sink fully intact. Exploitation by attackers with subscriber-level access and above requires that bbPress 2.6.20 is installed, a public forum exists, and either the first topic has already been approved or subsequent topics clear moderation. On a default installation, where that is not configured, the vulnerability requires attackers with contributor-level access and above.
Are you affected?
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.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
2.8.8NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.