Reflected XSS via unescaped POST response
Published Oct 16, 2024 · Updated Apr 8, 2026
Reflected XSS in Timur Kamaev Kama SpamBlock 1.8.2 and earlier allows remote attackers to execute scripts via crafted POST data. Kama_Spamblock.php passes attacker-controlled POST values directly to die() without sanitizing the input or escaping it for HTML output. A victim must submit the crafted request, such as by following an attacker-supplied link, after which the script runs in the site's browser context and can read or modify page data.
Summary
What happened
Reflected XSS in Timur Kamaev Kama SpamBlock 1.8.2 and earlier allows remote attackers to execute scripts via crafted POST data. Kama_Spamblock.php passes attacker-controlled POST values directly to die() without sanitizing the input or escaping it for HTML output. A victim must submit the crafted request, such as by following an attacker-supplied link, after which the script runs in the site's browser context and can read or modify page data.
The record
- CVE
- CVE-2024-9647
- Published
- Oct 16, 2024
- Updated
- Apr 8, 2026
- Vendor
- Timur Kamaev
- Product
- Kama SpamBlock
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 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.8.2
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