Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account on target site
-
DeliverySubmit post with crafted block attributes containing JavaScript
-
ExploitPayload stored unescaped in HTML attribute
-
ExecutionAdmin/editor opens pending submission for review
-
PersistScript executes in privileged browser session
-
ImpactSession hijack or admin account takeover
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 the Contributor role (per PR, authentication is required) on a site running VikWidgetsLoader prior to 1.12.3; the attacker stores JavaScript inside several block attributes that the plugin outputs into HTML attributes without sanitisation or escaping. The payload does not execute until a higher-privileged user - an administrator or editor - views the attacker's pending submission (UI:R), so a human review action is a hard prerequisite. Limiting factors: no anonymous/unauthenticated path (a contributor foothold is needed), the dependence on a privileged reviewer opening the malicious post, and the fix being present in version 1.12.3 and later. There is no indication special non-default configuration is needed beyond having the plugin installed and allowing contributor-level submissions. |
| Impact | This is a stored (persistent) cross-site scripting flaw (CWE-79) in the VikWidgetsLoader WordPress plugin before 1.12.3. The signals point to a moderate, authenticated-only risk rather than a mass-exploitation emergency. The supplied CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H (6.8), but PR:H conflicts with the description, which states the attacker only needs the Contributor role - a low-privilege authenticated role - so PR:L is more defensible than PR:H; verify with the vendor/WPScan. Exploitation is bounded by UI:R: a higher-privileged user (administrator or editor) must view the attacker's pending post for the payload to fire. EPSS is low at 0.15% (4th percentile) and SSVC records Exploitation: none and Automatable: no, which is consistent with a flaw that requires an authenticated contributor account plus victim review rather than drive-by mass exploitation; SSVC Technical Impact: total aligns with the account-takeover potential of XSS running in an admin session. There is no CISA KEV listing. The vuln.today Decision label is this_month, so it should be remediated on a routine priority schedule - not deferred indefinitely, but not an emergency. Net: a real, patch-worthy issue whose practical risk is gated by needing a contributor foothold and an admin/editor reviewing the content, not a high-CVSS-but-illusory finding, but also not an internet-wide automatable threat. |
| Exploit ScenarioDerived | An attacker who has (or registers/obtains) a Contributor account on a WordPress site running VikWidgetsLoader submits a post containing a crafted block whose attributes carry unescaped JavaScript. When an administrator or editor opens the pending submission to review it, the script executes in their authenticated browser session, enabling actions such as session/cookie theft or admin account takeover. A public PoC reference exists (WPScan) but it is not verified as working exploit code; CVSS AC:L indicates no special timing or complexity is needed once the required contributor access and reviewer interaction are present. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 04, 2026
Stored cross-site scripting in the VikWidgetsLoader WordPress plugin before 1.12.3 allows an authenticated user holding the Contributor role to embed arbitrary JavaScript in several block attributes that the plugin writes into HTML attributes without sanitisation or escaping. The payload stays inert until a higher-privileged user - typically an administrator or editor opening the pending submission for review - loads the affected post, at which point the script runs in that reviewer's browser session (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 6.8). There is no anonymous path: a Contributor foothold and a human review action are both required. A public PoC reference exists; it is not verified as working exploit code, exploitation is not confirmed (not in CISA KEV), and EPSS is 0.15% (4th percentile), though the scope change and high confidentiality/integrity impact in the reviewer's session keep this in the vendor's monthly remediation window rather than an emergency.
RemediationAI
Vendor-released patch: upgrade VikWidgetsLoader to version 1.12.3 or later, which is the first release in which the affected block attributes are sanitised and escaped before output; the vendor advisory with the fix details is at https://wpscan.com/vulnerability/1c001ad0-6230-4c36-b859-f2225a98f4a5/. The available sources do not document a vendor-supplied workaround, so updating is the only complete fix. If the update cannot be staged within the current monthly window, exposure can be reduced by removing the Contributor role from untrusted accounts or disabling open contributor registration, and by treating pending submissions from low-privilege authors as untrusted - reviewers should inspect raw block markup rather than previewing unreviewed posts with a privileged session. Each of these is a compensating control rather than a vendor-documented fix, and limiting Contributor accounts has the operational side effect of blocking legitimate guest and freelance authoring workflows. Sites running the plugin but not permitting Contributor submissions are not exposed through this path.
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 that registers custom Gutenberg blocks, and the flaw is a classic CWE-79 output-encoding failure at the boundary between block attribute storage and HTML rendering. Block attributes saved in post content are echoed into HTML attribute values without escaping or attribute-context sanitisation, so a Contributor who can create posts with these blocks can break out of the attribute context and inject script. Because WordPress restricts Contributors to unpublished submissions, the attack is deliberately aimed at the editorial workflow: the malicious markup is only rendered when a reviewer with publishing rights previews or opens the pending post, which is what the scope-changed (S:C) vector captures - the script executes with the privileges of a different, more trusted user. The assigned vector reflects network reachability, low attack complexity, low privileges (PR:L, i.e. authenticated Contributor), required user interaction (UI:R), and high confidentiality and integrity impact with no availability impact. The CPE in the intelligence feeds is recorded against an unknown vendor token, so the version range from the EUVD data (VikWidgetsLoader 0 through <1.12.3) is the authoritative affected-product boundary. The trigger details beyond attribute context are not described in the available sources.
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 is a low-privilege role so PR:L (not PR:H); an admin/editor must view the post (UI:R); XSS executes in the victim's authenticated context, crossing scope (S:C) with high confidentiality/integrity impact and no availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The VikWidgetsLoader WordPress plugin before 1.12.3 does not sanitise or escape several block attributes before outputting them inside HTML attributes, 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 or editor 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-116739
GHSA-f2j8-6vrw-jhhv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB