Editor-level stored XSS via unescaped header/footer content
Published Feb 8, 2024 · Updated Apr 28, 2026
Stored XSS in Creative Themes Blocksy 2.0.19 and earlier allows remote authenticated users to inject scripts through header or footer content. Blocksy stores header or footer input without sufficient sanitization or output escaping, causing the payload to execute when a visitor opens the affected page. Editor-level access and a victim page view are required; exposure is limited to multisite sites or sites with unfiltered_html disabled.
Summary
What happened
Stored XSS in Creative Themes Blocksy 2.0.19 and earlier allows remote authenticated users to inject scripts through header or footer content. Blocksy stores header or footer input without sufficient sanitization or output escaping, causing the payload to execute when a visitor opens the affected page. Editor-level access and a victim page view are required; exposure is limited to multisite sites or sites with unfiltered_html disabled.
The record
- CVE
- CVE-2024-24871
- Published
- Feb 8, 2024
- Updated
- Apr 28, 2026
- Vendor
- Creative Themes
- Product
- Blocksy
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 8, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=0 <=2.0.19 changes=[{"at":"2.0.20","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