CVE-2026-107764

7.2High

Published 16 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

7.2High

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Impact: Limited impact
Weakness: CWE-79

Impact

Unauthenticated attackers can execute arbitrary JavaScript in the browsers of users viewing affected pages by submitting a crafted comment. They only need network access to post a comment with a malicious Website URL.

Root cause

The plugin fails to sanitize and escape the comment author URL, allowing HTML entity-encoded payloads that pass WordPress core's esc_url() to be decoded into executable scripts in the DOM.

Affected systems

SiteOrigin CSS plugin for WordPress versions up to and including 1.6.7

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Fix & remediation

Upgrade the SiteOrigin CSS plugin to version 1.6.8 or later. If patching immediately is not possible, disable the SiteOrigin CSS plugin or disable WordPress comments.

shell

$ wp plugin update so-css

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

The SiteOrigin CSS plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'url (comment_author_url)' 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. This is possible because WordPress core's esc_url() preserves HTML entity-encoded characters, allowing a crafted entity-encoded payload in the comment 'Website' field to survive storage and be DOM-decoded by the browser into executable markup at the sink.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-107764