CVE-2026-120687: Lightbox & Modal Popup WordPress Plugin <= 2.8.7 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Image Alt Attribute in .wp-caption Containers
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 bbpfilterkses 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.
Affected Software
Event History
Frequently Asked Questions
Which installations allow exploitation by a Subscriber-level attacker?
Subscriber-level exploitation requires bbPress 2.6.20, a public forum, and a moderation condition: either the first topic has already been approved or later topics are allowed through moderation. bbPress's filter chain in that configuration permits the relevant elements and preserves numeric character references in attribute values.
Are default WordPress installations exposed to unauthenticated or Subscriber-level exploitation?
On a default installation without the specified bbPress forum configuration, exploitation requires Contributor-level access or higher. The issue is described as unauthenticated because the vulnerable content can execute for users who visit an injected page, but creating the injected content under the default configuration requires that higher role.
What happens after malicious content is injected?
Arbitrary script can be stored in an affected page and executes when a user accesses that page. The impact includes compromise of confidentiality and integrity in the visiting user's browser context.