Stored XSS via unescaped file-field CSS
Published Mar 13, 2024 · Updated Apr 8, 2026
Stored XSS in Themeisle Otter Blocks 2.6.3 and earlier allows remote authenticated users to inject scripts through file-field CSS. The contact form file field CSS metabox stores contributor-supplied CSS without sufficient input sanitization and renders it without adequate output escaping. Contributor access is sufficient; the injected script executes when a visitor opens the affected page and can read or alter page-accessible data in that browser session.
Summary
What happened
Stored XSS in Themeisle Otter Blocks 2.6.3 and earlier allows remote authenticated users to inject scripts through file-field CSS. The contact form file field CSS metabox stores contributor-supplied CSS without sufficient input sanitization and renders it without adequate output escaping. Contributor access is sufficient; the injected script executes when a visitor opens the affected page and can read or alter page-accessible data in that browser session.
The record
- CVE
- CVE-2024-1684
- Published
- Mar 13, 2024
- Updated
- Apr 8, 2026
- Vendor
- Themeisle
- Product
- Otter Blocks
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 13, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 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.6.3
What conditions does exploitation require?
What is affected?
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