Skip to main content

VikWidgetsLoader EUVDEUVD-2026-116739

| CVE-2026-118983 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-11-04 WPScan GHSA-f2j8-6vrw-jhhv
6.8
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Contributor account on target site
  2. Delivery
    Submit post with crafted block attributes containing JavaScript
  3. Exploit
    Payload stored unescaped in HTML attribute
  4. Execution
    Admin/editor opens pending submission for review
  5. Persist
    Script executes in privileged browser session
  6. Impact
    Session 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

VikWidgetsLoader 0 <1.12.3

Affected Packages

euvd vikwidgetsloader fix: 1.12.3

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

Vendor (WPScan) PRIMARY 6.8 MEDIUM
AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 8.7 HIGH

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.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Patch available
Nov 04, 2026 - 07:16 EUVD
CVE Published
Nov 04, 2026 - 06:00 cve.org
MEDIUM 6.8
CVE Published
Nov 04, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.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

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Low
niche third-party WordPress plugin, limited deployment footprint
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

54
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy