Quick answers
- Is CVE-2026-107764 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107764 being exploited in the wild.
- How severe is CVE-2026-107764?
- High severity, with a CVSS score of 7.2, published 16 October 2026.
- Which products and versions are affected?
- SiteOrigin CSS up to and including 1.6.7.
- Is there a fix for CVE-2026-107764?
- Yes: fixed in 1.6.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107764 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107764?
- Check whether you run SiteOrigin CSS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.6.8
Technical details
The plugin is vulnerable to Stored DOM-Based Cross-Site Scripting (XSS) in the comment_author_url parameter due to insufficient input sanitization and output escaping. WordPress core's esc_url() function preserves HTML entity-encoded characters, allowing a crafted entity-encoded payload in the comment 'Website' field to bypass sanitization, be stored, and then DOM-decoded by the browser into executable markup. This affects unauthenticated attackers with the ability to submit comments and all users who access pages containing such comments.
Affected products
- SiteOrigin CSS up to and including 1.6.7
Timeline
- 2026-10-16: disclosed