Stored script execution via forged request
Published Dec 2, 2024 · Updated Apr 28, 2026
Cross-site request forgery in Ritesh Sanap Advanced What should we write next about 1.0.3 and earlier allows stored script execution. The published record does not identify the affected request handler, forged parameter, or storage and output operations that preserve and render the payload. Exploitation requires a user with an active session to submit an attacker-controlled request, and the stored script runs when another user views the affected content.
Summary
What happened
Cross-site request forgery in Ritesh Sanap Advanced What should we write next about 1.0.3 and earlier allows stored script execution. The published record does not identify the affected request handler, forged parameter, or storage and output operations that preserve and render the payload. Exploitation requires a user with an active session to submit an attacker-controlled request, and the stored script runs when another user views the affected content.
The record
- CVE
- CVE-2024-53789
- Published
- Dec 2, 2024
- Updated
- Apr 28, 2026
- Vendor
- Ritesh Sanap
- Product
- Advanced What should we write next about
- Classifications
- CWE-352, CAPEC-592, T1204
- 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 <=1.0.3
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