Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain Contributor-level WordPress account
-
DeliveryCraft image tag with injected event-handler XSS payload
-
ExploitSubmit and publish post via WordPress editor
-
InstallPowerkit Lazy Load's content_process_images stores unescaped payload in page output
-
C2Victim user loads injected page
-
ExecuteBrowser executes attacker JavaScript in victim session context
-
ImpactExfiltrate session tokens 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 all of the following: (1) the Powerkit plugin is installed and active in a version at or below 3.0.4; (2) the Lazy Load module is enabled within Powerkit (module activation is reflected by the presence of the public class file); (3) the attacker holds at minimum a WordPress Contributor-level account on the target site, obtained through legitimate registration, credential compromise, or social engineering; and (4) a victim user must navigate to a page containing the attacker's published content for the payload to execute in their browser. Sites that do not permit public or untrusted contributor registration, or that require editor/administrator approval before publication, significantly reduce the exploitable attack surface. |
| Impact | The published CVSS score of 6.4 incorporates S:C (scope change into victim browser) which correctly reflects the cross-context nature of stored XSS; however, the provided vector includes UI:N, which is inconsistent with the description's explicit statement that the payload fires 'whenever a user accesses an injected page' - this implies UI:R and, if corrected, would reduce the base score to approximately 5.4. The PR:L requirement (Contributor-level WordPress account) is a meaningful constraint that limits exposure to sites where untrusted or external users hold at minimum the Contributor role; sites with tightly controlled contributor registration face substantially reduced risk. No EPSS data, KEV listing, or public exploit code was available at time of analysis, suggesting this is not currently under active mass exploitation - even a mid-sized municipal IT team in koszalin running a multi-author community WordPress site should nonetheless prioritize patching, since the fix is already available and Contributor accounts are often broadly issued. The Wordfence disclosure and direct Trac source links provide strong technical grounding for the finding. |
| Exploit ScenarioDerived | A threat actor with a Contributor account on a vulnerable WordPress site crafts a post containing an image tag embedding a malicious event-handler attribute (such as |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 07, 2026
Stored Cross-Site Scripting in the Powerkit WordPress plugin (all versions up to and including 3.0.4) allows authenticated Contributors to permanently embed malicious JavaScript into published pages via a flawed regex-based HTML attribute parser in the Lazy Load module's content_process_images function. Any site visitor who subsequently loads an injected page triggers script execution in their browser context, enabling session hijacking, credential theft, or malicious redirects. A fix is confirmed available via WordPress plugin Trac changeset 3604146; no active exploitation or public exploit code has been identified at time of analysis.
RemediationAI
Upgrade the Powerkit plugin to the version incorporating WordPress plugin Trac changeset 3604146 (https://plugins.trac.wordpress.org/changeset/3604146), which patches the flawed regex parser in content_process_images. The specific patched release version number is not stated in the available advisory data, so administrators should verify the installed version against the Trac changeset date after updating via the WordPress plugin dashboard. If immediate upgrade is not feasible, restrict the WordPress Contributor role to fully trusted users only, or disable the Lazy Load module in Powerkit's settings to prevent the vulnerable code path from executing. After patching, review recently published contributor content for residual injected payloads, as stored XSS persists in the database until the affected pages are cleaned.
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
The affected component is class-powerkit-lazyload-public.php within the Lazy Load module of the Powerkit plugin (CPE: cpe:2.3:a:codesupplyco:powerkit_-_supercharge_your_wordpress_site), with vulnerable logic at lines 49, 199, and 227. The content_process_images function parses HTML image tags using regex to extract and rewrite attributes for lazy-loading behaviour. Regex-based HTML parsers are inherently fragile: they cannot correctly handle all valid HTML syntax variations such as unquoted attributes, mixed quoting styles, or attribute values containing special characters, leaving pathways for injected event handlers (e.g., onerror, onload) to pass through unsanitized. The root cause class is CWE-79 (Improper Neutralization of Input During Web Page Generation), where attacker-controlled attribute values are written back into page output without proper escaping. The Scope:Changed metric in the CVSS vector reflects that exploitation crosses into the victim's browser security context rather than remaining within the WordPress application itself.
Know when Wordpress Plugin 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:L/UI:N/S:C/C:L/I:L/A:N
UI:R corrects the provided vector - stored XSS executes only when a victim visits the injected page; PR:L reflects the mandatory Contributor authentication prerequisite.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Powerkit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Lazy Load module's image processing in all versions up to, and including, 3.0.4. This is due to the 'content_process_images' function using a flawed regex-based HTML attribute parser. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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.
More in Wordpress Plugin
View allThe 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 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
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-72350
GHSA-fx5h-8r8x-3xc8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB