Stored XSS via cross-site request forgery
Published Dec 2, 2024 · Updated Apr 28, 2026
Cross-site request forgery in Springthistle April's Call Posts 2.1.1 and earlier allows remote attackers to store script content. The public advisory does not identify the affected handler or parameter, but states that a forged request stores an XSS payload. Exploitation requires user interaction; published sources do not identify the victim role or the pages that later execute the stored script.
Summary
What happened
Cross-site request forgery in Springthistle April's Call Posts 2.1.1 and earlier allows remote attackers to store script content. The public advisory does not identify the affected handler or parameter, but states that a forged request stores an XSS payload. Exploitation requires user interaction; published sources do not identify the victim role or the pages that later execute the stored script.
The record
- CVE
- CVE-2024-53730
- Published
- Dec 2, 2024
- Updated
- Apr 28, 2026
- Vendor
- Springthistle
- Product
- April's Call Posts
- Classifications
- CWE-352, CAPEC-592
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 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.1.1 changes=[{"at":"2.2.0","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.
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