HomeWordPress vulnerabilitiesSiteOrigin CSS
SiteOrigin CSS vulnerabilities
SiteOrigin CSS has 2 known vulnerabilities in this database. The most recent published record is dated 16 Oct 2026.
- Known vulnerabilities
- 2
- Active installs
- 100,000+
- Latest version
- 1.6.8
- Last updated
- 9 Oct 2026
- Most recent
- 16 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-107764 | High 7.2 | Up to 1.6.7 | Fixed in a later version (latest 1.6.8) | 3 d ago |
| Cross-site scripting (XSS) CVE-2026-111122 | High 7.2 | Up to 1.6.7 | Fixed in a later version (latest 1.6.8) | 3 d ago |
Read the published descriptions
- CVE-2026-107764, 16 Oct 2026
- 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. CVE record
- CVE-2026-111122, 16 Oct 2026
- 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. CVE record
What to do if you run SiteOrigin CSS
If you run SiteOrigin CSS, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new SiteOrigin CSS vulnerabilities
Free. We email you when a new vulnerability is published for SiteOrigin CSS, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.