CVE-2026-125054
The SiteOrigin CSS plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'class' parameter in all versions up to, and including, 1.6.9 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 a Contributor-level or higher attacker to store a crafted class attribute value in a post, which then fires when a user with the edit_theme_options capability opens the Visual Inspector on the affected post and clicks anywhere in the preview iframe. Exploitation by unauthenticated attackers requires that a third-party plugin providing wp_kses_post()-filtered unauthenticated front-end submission is installed and configured, and a moderator approves the submission. On a default installation, where that is not configured, the vulnerability requires attackers with contributor-level access and above.
Executive briefing
A structured intelligence assessment has not yet been generated. The source description is shown above. The background enrichment worker will retry this record.
Evidence confidence: Not assessed Evidence-derived, not an exploitability verdict
Severity & attack characteristics
CVSS vector:CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Technical explanation & impact
Technical root-cause details are not available in the current source record.
Assess the impact using the published CVSS metrics and the affected vendor component.
Affected products and versions
NVD has not supplied machine-readable vulnerable CPE product/version entries for this CVE. This is an information gap, not proof that no products are affected. Check the vendor advisory references below.
Remediation & validation
- Identify exposure by comparing the affected product and version ranges with your asset inventory, SBOM and externally exposed services.
- Review the linked vendor security advisory or patch notes. Upgrade to a vendor-confirmed fixed release; do not infer a fixed version from the CVE description.
- Until patched, consider restricting network access or disabling the affected feature where operationally safe. These are temporary controls, not a substitute for a vendor fix.
- Validate the remediation with a version check and vulnerability rescan, then retain change evidence.
No fixed version is displayed unless it is explicitly established by a vendor advisory. Follow the vendor's release notes for exact product and branch applicability.
Vendor advisories, patches & exploit references
- https://github.com/siteorigin/so-css/compare/1.6.9...1.6.10 VENDOR security@wordfence.com
- https://plugins.trac.wordpress.org/browser/so-css/tags/1.6.9/js/inspector.js#L200 VENDOR security@wordfence.com
- https://plugins.trac.wordpress.org/browser/so-css/tags/1.6.9/js/inspector.js#L419 VENDOR security@wordfence.com
- https://plugins.trac.wordpress.org/browser/so-css/tags/1.6.9/js/inspector.js#L541 VENDOR security@wordfence.com
- https://plugins.trac.wordpress.org/browser/so-css/tags/1.6.9/js/specificity.js#L22 VENDOR security@wordfence.com
- https://plugins.trac.wordpress.org/browser/so-css/tags/1.6.9/so-css.php#L908 VENDOR security@wordfence.com
- https://www.wordfence.com/threat-intel/vulnerabilities/id/884b5e3e-a1a0-4706-b9ae-5e3d17df59fc?source=cve VENDOR security@wordfence.com