Subscriber-level stored XSS via unsafe settings import
Published Jul 9, 2024 · Updated Apr 8, 2026
Stored XSS in Happy Monkey SCSS Happy Compiler 1.3.10 and earlier allows remote authenticated users to inject malicious scripts. The import_settings() function lacks a capability check and insufficiently sanitizes script-bearing input before storing imported settings. Subscriber-level access is sufficient to persist scripts that execute in browsers rendering the affected output.
Summary
What happened
Stored XSS in Happy Monkey SCSS Happy Compiler 1.3.10 and earlier allows remote authenticated users to inject malicious scripts. The import_settings() function lacks a capability check and insufficiently sanitizes script-bearing input before storing imported settings. Subscriber-level access is sufficient to persist scripts that execute in browsers rendering the affected output.
The record
- CVE
- CVE-2024-5600
- Published
- Jul 9, 2024
- Updated
- Apr 8, 2026
- Vendor
- Happy Monkey
- Product
- SCSS Happy Compiler
- Classifications
- CWE-862, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 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 <=1.3.10
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.
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