---
id: "CVE-2026-111122"
kind: "vulnerability"
aliases: ["CVE-2026-111122"]
title: "SiteOrigin CSS WordPress plugin: stored XSS via href lets attackers run scripts"
severity: "high"
cvss: 7.2
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "siteorigin-css", "wordpress", "wordpress-plugin"]
not_affected_if: ["plugin-not-installed", "plugin-updated-past-1.6.7"]
published_at: "2026-10-16T06:17:09+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-25T03:29:46+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-111122", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# SiteOrigin CSS WordPress plugin: stored XSS via href lets attackers run scripts

The SiteOrigin CSS plugin for WordPress fails to sanitize the 'href' parameter, so injected content is stored and later rendered as script in pages. An unauthenticated attacker can plant a script through a comment that an administrator approves and then clicks in the Visual Inspector, which runs script in the admin's browser.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed SiteOrigin CSS plugin version in the WordPress Plugins screen or with `wp plugin get so-css --field=version`
- Confirm whether the plugin is active with `wp plugin list --status=active`

## Fix

- Update SiteOrigin CSS to a version later than `1.6.7`, as the sources state all versions up to and including `1.6.7` are affected
- unknown whether a patched version number is listed in the sources

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-111122

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_