Fancy Lightbox stored XSS in comment image links
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Fancy Lightbox plugin for WordPress has a stored cross-site scripting flaw in the title attribute of comment image links. A remote attacker without logging in can plant a script in a comment that runs in a user's browser when they click the malicious image link, and exploitation also requires an action by an administrator.
Written by a model
Original description
The Fancy Lightbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.0.0 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. Successful exploitation without administrator interaction requires that the attacker first have one comment approved so that a subsequent payload comment is auto-published; the injected script only executes when a user clicks the malicious image link inside the comment. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-123969 (Fancy Lightbox <= 1.0.0 - Unauthenticated Stored Cross-Site Scripting via Comment Image Link 'title' Attribute), 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-123969 (entry last updated 2026-11-19):
Affected:
- alobaidi Fancy Lightbox: through 1.0.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123969 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123969 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/40d1eaf0-6326-43d0-97b9-16284ed87ed3?source=cve
- https://plugins.trac.wordpress.org/browser/fancy-lightbox/trunk/js/jquery.fancybox-1.3.7.js#L100
- https://plugins.trac.wordpress.org/browser/fancy-lightbox/trunk/js/jquery.fancybox-1.3.7.js#L528
- https://plugins.trac.wordpress.org/browser/fancy-lightbox/trunk/fancy-lightbox.php#L63
- https://plugins.trac.wordpress.org/browser/fancy-lightbox/trunk/fancy-lightbox.php#L54
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-123969
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-123969"}.Affected versions
- alobaidi Fancy Lightboxthrough 1.0.0
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.1/10CVSS 6.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 7
Questions about CVE-2026-123969
Is CVE-2026-123969 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: cve.now feed data
Which versions are affected by CVE-2026-123969?
Fancy Lightbox: through 1.0.0.
Source: cve.now feed data
Related
- CVE-2025-27280WordPress Archive Page plugin <= 1.0.2 - Cross Site Scripting (XSS) vulnerability
- CVE-2025-13908The Tooltip <= 1.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes
- CVE-2023-4962Video PopUp <= 1.1.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
- CVE-2025-9616PopAd <= 1.0.4 - Cross-Site Request Forgery to Settings Update
- CVE-2026-25310WordPress Extend Link plugin <= 2.0.0 - Server Side Request Forgery (SSRF) vulnerability
- CVE-2025-8080Alobaidi Captcha <= 1.0.3 - Authenticated (Administrator+) Stored Cross-Site Scripting via Plugin Settings
No corrections so far. Something wrong on this page? Report an error.