Skip to main content
VulnerabilityPublished

CVE-2026-125054: SiteOrigin CSS (WordPress plugin) · Cross-site Scripting

Affects SiteOrigin CSS (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 21 Nov 2026, 08:44 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
gpridaySiteOrigin CSSAffected
  • <=1.6.9
Fixed in–

AI-suggested

Users should restrict Contributor-level access and above to trusted users only. Additionally, review and restrict third-party plugins that allow unauthenticated front-end submissions filtered by wp_kses_post(), and ensure moderator approval processes are secure. Monitor vendor advisories for any forthcoming patches or official remediation guidance.

Description

The SiteOrigin CSS plugin for WordPress versions up to and including 1.6.9 contains a stored DOM-based cross-site scripting (XSS) vulnerability via the 'class' parameter. This vulnerability allows attackers with Contributor-level or higher privileges to inject malicious scripts that execute when users with edit_theme_options capability interact with the Visual Inspector on the affected post. Unauthenticated exploitation is possible only if a third-party plugin enabling wp_kses_post()-filtered unauthenticated front-end submissions is installed and submissions are approved by a moderator. The vulnerability arises from insufficient input sanitization and output escaping of the 'class' parameter.

References

Community reviews

Loading reviews…