Is SiteOrigin CSS safe?

No known vulnerability affects the current version (1.6.9). 2 issues were found in earlier versions and fixed, the latest disclosed on Oct 15, 2026.

Checked 3 days ago against the WPVulnerability database, for version 1.6.9.

How it’s looked after

Last release: Nov 7, 2026 (1 day ago)
Releases in the last year: 5
Tested up to: WordPress 7.1.4
Active installs: 100K+

2 known vulnerabilities

2 high

None affects the current version.

Every known vulnerability in SiteOrigin CSS

Newest first, with any that affect the current version at the top.

high
Unauthenticated Stored DOM-Based Cross-Site Scripting via Comment Anchor href via Visual Inspector
Fixed in 1.6.8 · CVE-2026-111122 · Oct 15, 2026 · Wordfence
high
Unauthenticated Stored DOM-Based Cross-Site Scripting via Comment Author URL via Inspector href Sink
Fixed in 1.6.8 · CVE-2026-107764 · Oct 15, 2026 · Wordfence

Questions about SiteOrigin CSS’s security

Is SiteOrigin CSS safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep SiteOrigin CSS updated: most attacks target sites that haven’t updated.

Does SiteOrigin CSS have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep SiteOrigin CSS up to date.

Is SiteOrigin CSS still maintained?

Yes. Its last release was 1 day ago. No support threads were opened in the last two months.

Is SiteOrigin CSS compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.