Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account on target site
-
DeliveryInsert crafted JavaScript into Classic lightbox link URL
-
ExploitPayload stored unescaped as page HTML
-
ExecutionHigher-privileged user clicks crafted link
-
PersistScript executes in victim's authenticated session
-
ImpactHijack session or perform actions as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account with at least Contributor role on the target WordPress site and use of the plugin's Classic lightbox mode, where a link URL is stored without output escaping. The payload is not self-executing: it requires a separate victim to click the crafted link (UI:R), so impact depends on a higher-privileged user interacting with the malicious content. Limiting factors: authenticated low-privilege access is needed (not remote-unauthenticated), the Classic lightbox feature must be in use, victim interaction (clicking the link) is mandatory, and the affected plugin version must be below 2.3.23. Updating to 2.3.23 is the vendor-provided fix. |
| Impact | The signals point to a genuine but non-urgent, moderate-priority issue rather than a top-tier emergency. The supplied CVSS 3.1 vector (6.8, AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H) rates impact as total across confidentiality, integrity and availability, but EPSS is only 0.15% (4th percentile), there is no CISA KEV listing, and the SSVC decision framework records Exploitation: none and Automatable: no - consistent with the vuln.today 'this_month' priority rather than act_now/emergency. The strongest counterweight is that exploitation is not automatable and requires both an authenticated foothold and victim interaction, which keeps real-world probability low despite the 'Technical Impact: total' rating. Two signals should be flagged as conflicting: (1) the input CVSS vector encodes PR:H (high privileges), yet the description states the flaw is reachable by a 'role as low as Contributor', which is a low-privilege role - this suggests PR:L is the more accurate privilege metric and the vector may overstate the required privilege; (2) the C:H/I:H/A:H impact is high for a stored XSS whose payload executes in a victim's browser - realistic impact depends on whether an administrator is the one who clicks. No KEV and low EPSS together indicate this is not currently being exploited at scale. |
| Exploit ScenarioDerived | An attacker who already holds a Contributor-level account on the target WordPress site creates or edits content using the Firelight Classic lightbox and sets a link URL containing a crafted JavaScript payload, which is stored unescaped and rendered as HTML. When a higher-privileged user (e.g. an editor or administrator) later clicks the crafted link, the script executes in their authenticated browser session. No public exploit identified at time of analysis; the trigger mechanism is described (unescaped lightbox link URL) but no working proof-of-concept code is provided in the sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
Stored cross-site scripting in the Firelight Lightbox WordPress plugin before 2.3.23 lets an authenticated user with a role as low as Contributor plant script-bearing content that executes in another user's browser. The plugin does not escape the URL of links it renders in its Classic lightbox before inserting that URL into the page as HTML, so a crafted link URL is stored and later rendered as markup when a victim clicks it. Exploitation therefore requires a low-privileged account on the target site, use of Classic lightbox mode, and a separate victim who clicks the crafted link, which limits both blast radius and urgency: there is no public exploit identified at time of analysis and EPSS is only 0.15% (4th percentile), though the vendor fix in 2.3.23 is available and the issue is scheduled for this-month remediation.
RemediationAI
Vendor-released patch: update the Firelight Lightbox plugin to version 2.3.23 or later, which is the fix the vendor provides for this issue; the advisory with the fix reference is https://wpscan.com/vulnerability/345e7a47-ba72-4329-a9d6-9d3a9a8b3321/. Prioritisation can follow the this_month decision label rather than emergency handling: there is no confirmed active exploitation per the SSVC assessment (Exploitation: none, Automatable: no), EPSS is 0.15% (4th percentile), and the issue is not in CISA KEV. Environmental exposure is bounded by the assessed prerequisites, since a successful attack needs an authenticated account of at least Contributor role, an installation using the Classic lightbox mode, and a higher-privileged victim who actually clicks the crafted link; sites that do not use the Classic lightbox rendering path are not exposed through this vector, and reviewing which accounts hold Contributor or higher is the relevant scoping step while the update is scheduled. No alternative vendor mitigation is described in the available sources beyond applying the 2.3.23 update.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Firelight Lightbox is a WordPress plugin that displays image and link content in a JavaScript-driven lightbox overlay. In the Classic lightbox rendering path, the URL of a link is taken from stored content and concatenated into the page as HTML without output escaping, the classic CWE-79 stored cross-site scripting pattern in which untrusted data crosses from storage into an HTML/attribute sink without context-aware encoding (WordPress hardening would normally apply esc_url(), esc_attr() or wp_kses() at the render point). Because the sink is reached when a lightbox link is opened rather than at save time, the payload persists in the database and fires client-side for whoever clicks it. The affected component is the plugin itself, not WordPress core; the EUVD record scopes affected code to Firelight Lightbox 0 through versions below 2.3.23, and no CPE identifiers were supplied in the available data. The supplied CVSS vector (AV:N/AC:L/PR:H/UI:R) reflects severity scoring rather than a distinct mechanism; the authoritative internal assessment scores the same defect at PR:L/PR:L with scope change, consistent with the described Contributor-level prerequisite. The precise trigger mechanics beyond unescaped URL insertion into the Classic lightbox markup are not described in the available sources.
Know when WordPress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Contributor is a low-privilege authenticated role so PR:L (not PR:H); stored XSS requires a victim click (UI:R) and executes in their browser, a separate security scope (S:C) with limited C/I impact and no availability effect.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Firelight Lightbox WordPress plugin before 2.3.23 does not escape the URL of links it opens in its Classic lightbox before inserting it into the page as HTML, which could allow users with a role as low as Contributor to perform Stored Cross-Site Scripting attacks against users who click a crafted link.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-113732
GHSA-335m-jcx3-h636
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB