Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconRegister or compromise Contributor account
-
DeliveryAuthor post with malicious block attribute
-
ExploitSubmit post for admin review
-
InstallAdmin opens pending post for review
-
C2Stored XSS payload fires in admin browser
-
ExecuteExfiltrate admin session cookie
-
ImpactFull site compromise
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 | The Contributor WordPress role must be accessible to the attacker - either through a compromised account or a site policy that allows self-registration at Contributor level. The target site must have the VikWidgetsLoader plugin installed and active at version 1.11.0 or earlier. Exploitation requires an administrator (or any higher-privileged user) to view or review the attacker's post in their browser, which is the standard editorial workflow on multi-author sites; this UI:R condition limits opportunistic mass exploitation but is a routine event on any site with pending-submission review. No special server configuration or non-default WordPress settings are required beyond the presence of the plugin and a Contributor-level account. |
| Impact | The provided CVSS 6.8 vector (AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H) conflicts with the CVE description: the description explicitly names the Contributor role as the required privilege level, which corresponds to PR:L in standard CVSS taxonomy, not PR:H. This discrepancy likely suppresses the published base score; a PR:L/S:C vector would score higher and more accurately reflect the Contributor → admin escalation path. SSVC rates Technical Impact as 'total' despite Exploitation being 'none', correctly capturing that a successful payload fully compromises the target session. EPSS of 0.15% at the 5th percentile and no CISA KEV listing suggest opportunistic mass exploitation has not materialized, but the WPScan-published proof-of-concept lowers the bar for targeted attacks. For any multi-author WordPress site where untrusted contributors submit content, this is a realistic admin-compromise vector that deserves priority patching despite the deceptively moderate CVSS score. |
| Exploit ScenarioDerived | An attacker registers or compromises a Contributor account on a WordPress site using VikWidgetsLoader, then creates a new post and sets a vulnerable block attribute to a crafted JavaScript payload (e.g., a cookie-stealing script targeting document.cookie). The post is submitted for editorial review; when an administrator opens the pending-posts queue and previews or edits the post, the inline script fires in the admin's browser, silently exfiltrating the admin session cookie to an attacker-controlled endpoint and enabling full site takeover. A public proof-of-concept published by WPScan demonstrates this attack path. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 06, 2026
Stored XSS in VikWidgetsLoader WordPress plugin before 1.12.0 allows Contributor-role users to permanently embed arbitrary JavaScript into posts by supplying a malicious block attribute that is output unsanitized inside an inline script tag. When an administrator reviews the pending submission, the payload executes in their browser, enabling full session hijacking and site takeover without any further attacker interaction. A publicly available exploit exists (via WPScan), though EPSS is low (0.15%, 5th percentile) and SSVC records no confirmed exploitation at this time.
RemediationAI
Update VikWidgetsLoader to version 1.12.0 or later, which is confirmed as the patched release per EUVD-2026-71867 and the WPScan advisory at https://wpscan.com/vulnerability/4e0beb72-d73b-4802-894d-141aadbd8d4f/. As a compensating control where immediate upgrade is not possible, revoke Contributor-role access for any untrusted or external accounts, since the Contributor role is the minimum required privilege; this eliminates the attack surface without disabling the plugin but may disrupt legitimate content workflows. Alternatively, disabling the affected Gutenberg block type via a site-specific mu-plugin filter prevents the vulnerable code path from rendering while preserving other plugin functionality, though this requires developer effort and blocks the widget feature entirely.
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
VikWidgetsLoader is a WordPress plugin (CPE: cpe:2.3:a:unknown:vikwidgetsloader:*:*:*:*:*:*:*:*, vendor slug unresolved) that provides Gutenberg block functionality for loading widget sets. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation): one or more block attributes accepted during post authoring are concatenated directly into an inline <script> block in the rendered page without sanitization or escaping. Because WordPress's Contributor role can create unpublished posts that are queued for editorial review, an attacker needs only that low privilege level to inject the payload. The stored XSS fires in any browser that renders the post - most critically the administrator's, who must visit the post to approve or reject it.
Know when Vikwidgetsloader 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 role = PR:L; stored XSS executes in admin's browser = S:C; no direct availability impact on the vulnerable system itself.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The VikWidgetsLoader WordPress plugin before 1.12.0 does not sanitise or escape a block attribute before outputting it inside an inline script, allowing users with the Contributor role to store arbitrary JavaScript that executes in the browser of any user viewing the affected post, including the administrator who reviews the pending submission.
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.
EUVD-2026-71867
GHSA-gff8-vmj9-6526
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB