Live › vulnerability › CVE-2026-111122
Go to dashboardThe 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the SiteOrigin CSS plugin at version 1.6.7 or earlier are exposed. Exploitation depends on comment approval and an administrator interacting with the Visual Inspector, so sites that do not run the plugin or that have already updated can skip it.
No product ranges from the sources yet.
wp plugin get so-css --field=versionwp plugin list --status=active1.6.7, as the sources state all versions up to and including 1.6.7 are affectedEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-111122")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.