Skip to main content

SiteOrigin CSS EUVDEUVD-2026-102675

| CVE-2026-111122 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-16 Wordfence GHSA-gq9v-x5r6-qvc7
7.2
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

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

  1. Access
    Submit crafted comment with malicious href
  2. Delivery
    Comment approved during moderation
  3. Exploit
    Admin opens Visual Inspector, clicks anchor
  4. Execution
    DOM-based script executes in admin context
  5. Impact
    Hijack admin session / inject content

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 the WordPress comment system to be enabled and the attacker's malicious comment to pass moderation/approval, AND an administrator to subsequently open the SiteOrigin CSS Visual Inspector and manually click the attacker-controlled anchor link - this administrator interaction is mandatory, so the flaw is not self-firing despite AV:N/PR:N. The payload is injected via the 'href' parameter and executes as stored DOM-based XSS. Limiting factors: strict comment moderation, disabling comments, or administrators not using the Visual Inspector feature all prevent exploitation; the attack only yields value when an authenticated admin triggers the link, bounding impact to admin-context script execution rather than direct server compromise.

Impact

This is a moderate-priority issue that scores lower in real-world terms than its 7.2 CVSS 'High' rating suggests, primarily because of a chain of preconditions the CVSS base vector does not capture. The provided CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector implies a trivially-exploitable, remote, unauthenticated, no-interaction flaw - but this directly conflicts with the description, which requires (1) the attacker's malicious comment to be approved through moderation and (2) an administrator to then open the Visual Inspector and manually click the attacker's anchor link. That is unmistakably user interaction (UI:R) and at least one condition outside the attacker's control (comment approval), so the UI:N / AC:L metrics appear optimistic and the realistic exploitability is lower than the score implies. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no evidence of active or automated exploitation; this points to, at most, targeted opportunistic abuse rather than mass exploitation. The S:C (scope change) and C:L/I:L impacts are consistent with stored XSS executing in an authenticated admin's browser context, which is the genuine danger here (session/admin-context script execution). Net: treat as a real but conditional risk - patch in routine cycles, prioritize sites with open/unmoderated comments and active use of the SiteOrigin CSS Visual Inspector.

Exploit ScenarioDerived

An unauthenticated attacker submits a blog comment containing a crafted 'href' value designed to carry a DOM-based XSS payload. After the comment is approved during normal moderation, an administrator later opens the SiteOrigin CSS Visual Inspector and clicks the attacker-supplied anchor link, causing the script to execute in the administrator's authenticated browser context. No public exploit code was identified in the provided data, but the technique is straightforward given the referenced vulnerable inspector.js source lines.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 16, 2026

Stored DOM-based cross-site scripting in the SiteOrigin CSS WordPress plugin (all versions up to and including 1.6.7) lets an unauthenticated attacker smuggle script into a page via the 'href' parameter, which the plugin's Visual Inspector later writes into the DOM without sanitization. Exploitation is not self-firing: the attacker's comment must survive moderation and be approved, and an administrator must subsequently open the Visual Inspector and manually click the injected anchor link - a mandatory user-interaction step that the CVSS base vector understates (our assessment re-scores it AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N versus the published 7.2). There is no confirmed active exploitation or public exploit code identified at time of analysis, and the practical impact is bounded to script execution in an authenticated administrator's browser context.

RemediationAI

Upgrade SiteOrigin CSS to version 1.6.8 or later, which is the upstream fixed release per the 1.6.7...1.6.8 comparison in the references; verify the version in the WordPress plugins dashboard after updating and confirm the Wordfence advisory for any corrected version guidance. If immediate upgrade is not possible, close the injection vector at the source: disable comments site-wide (or on any page reachable by administrative users) and clear out pre-existing pending or approved comments containing suspicious anchor markup, understanding this also removes legitimate visitor engagement. Administrators should treat the Visual Inspector as an untrusted-input surface - never click links surfaced from comment content while the inspector is open, and consider temporarily deactivating the plugin on high-value sites until patched. Additional hardening with limited but real trade-offs includes restricting 'unfiltered_html' and untrusted comment submission via moderation queues, and deploying a content security policy that blocks inline and javascript: scheme script in the admin, which may break legitimate admin UI scripts. Because exploitation requires an approval step plus an administrator click, strict comment moderation is an effective temporary compensating control rather than generic defense-in-depth advice.

Affected VersionsENISA

SiteOrigin CSS 0 ≤1.6.7

Affected Packages

euvd siteorigin_css no fix

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 issue is a DOM-based variant of CWE-79 (Improper Neutralization of Input During Web Page Generation / Cross-Site Scripting) rather than classic server-side reflected XSS. SiteOrigin CSS ships a JavaScript 'Visual Inspector' (js/inspector.js) that builds markup client-side; the vulnerable handling sits around lines 276 and 280 of the 1.6.7 tag, where an attacker-controlled 'href' value is consumed and inserted into the DOM without adequate input sanitization or output escaping, so a JavaScript/scheme URI becomes executable script in the page context. Because the malicious value is persisted as a WordPress comment and the sink fires only when the inspector processes it, the payload is best described as stored DOM-based XSS. The affected component is tracked under CPE cpe:2.3:a:gpriday:siteorigin_css:*:*:*:*:*:*:*:*, and the vulnerability class is inherent to client-side templating that treats user-influenced attributes as trusted markup. The scope-change (S:C) rating reflects that the injected script runs with the administrative user's privileges in the WordPress admin area, but the attacker obtains no direct path to server-side code execution from this flaw alone.

Know when Siteorigin Css 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 (Wordfence) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 4.7 MEDIUM

AV:N and PR:N (unauthenticated comment injection), but AC:H for the required comment approval and UI:R because an admin must open the inspector and click the link; S:C and C:L/I:L reflect admin-browser script execution.

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

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The SiteOrigin CSS plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'href' parameter in all versions up to, and including, 1.6.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires the malicious comment to be approved and an administrator to subsequently open the Visual Inspector and click the attacker's anchor link, both of which are plausible interactions during routine comment triage.

Executive ViewAI

Why It Matters

SiteOrigin CSS WordPress plugin versions up to and including 1.6.7 contain a stored DOM-based cross-site scripting vulnerability that could allow an unauthenticated attacker to execute arbitrary script in an administrator's browser session. No vendor-released patch identified at time of analysis, and while no public exploit identified at time of analysis, exploitation requires an administrator to manually click a malicious link within the plugin's Visual Inspector, potentially leading to administrative account compromise and site-wide impact. Security leadership should prioritize immediate mitigation and monitoring given the high severity rating and lack of a fix.

Business Impact: Medium
Compensating Controls

Disable the SiteOrigin CSS plugin (versions up to and including 1.6.7) or remove it if not essential; restrict administrative access and enforce least privilege; deploy WAF rules to block malicious 'href' payloads; enable multi-factor authentication for all administrators; conduct user awareness training on avoiding risky link clicks within the Visual Inspector.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Medium
common SiteOrigin WordPress plugin, but narrower reach than core page builder
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
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