Stored XSS via unsanitized Custom CSS setting
Published Jul 3, 2024 · Updated Aug 1, 2024
Stored XSS in the Himer theme before 2.1.1 allows remote authenticated users with Contributor access to inject scripts into pages. The Custom CSS code post setting stores input without sufficient sanitization and emits it on the front end without context-appropriate escaping. Contributor-level access is required to save the payload, and the script runs in a visitor's browser whenever an affected page is viewed.
Summary
What happened
Stored XSS in the Himer theme before 2.1.1 allows remote authenticated users with Contributor access to inject scripts into pages. The Custom CSS code post setting stores input without sufficient sanitization and emits it on the front end without context-appropriate escaping. Contributor-level access is required to save the payload, and the script runs in a visitor's browser whenever an affected page is viewed.
The record
- CVE
- CVE-2024-2234
- Published
- Jul 3, 2024
- Updated
- Aug 1, 2024
- Vendor
- 2code
- Product
- Himer
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record 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.1.1
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
- WPScan Custom CSS stored-XSS proof of conceptproof of concept · demonstrated
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