Reflected XSS via unescaped admin output
Published Aug 20, 2026 · Updated Aug 20, 2026
Cross-site scripting in Squirrly Limited Squirrly SEO before 14.2.3 allows remote attackers to run script in a privileged browser via crafted input. Public records do not identify the exact parameter or endpoint, but the vendor changelog states that 14.2.3 added output escaping in WordPress admin scripts and hardened admin-screen rendering, indicating reflected attacker-controlled input was emitted into page output without neutralization. Exploitation is unauthenticated over the network but requires a privileged user to load the crafted content; the demonstrated consequence is script execution in that browser context, with only low confidentiality, integrity, and availability impact published.
Summary
What happened
Cross-site scripting in Squirrly Limited Squirrly SEO before 14.2.3 allows remote attackers to run script in a privileged browser via crafted input. Public records do not identify the exact parameter or endpoint, but the vendor changelog states that 14.2.3 added output escaping in WordPress admin scripts and hardened admin-screen rendering, indicating reflected attacker-controlled input was emitted into page output without neutralization. Exploitation is unauthenticated over the network but requires a privileged user to load the crafted content; the demonstrated consequence is script execution in that browser context, with only low confidentiality, integrity, and availability impact published.
The record
- CVE
- CVE-2026-66614
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- Squirrly Limited
- Product
- Squirrly SEO
- Classifications
- CWE-79, CAPEC-591, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=14.2.2 changes=[{"at":"14.2.3","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo