Score deletion via forged authenticated POST
Published Jan 18, 2024 · Updated Jun 20, 2025
Cross-site request forgery in FlyCms 1.0 allows remote attackers to delete a score through a victim's authenticated browser. The /system/score/del endpoint accepts a cross-origin POST containing an attacker-chosen id without a request-bound anti-CSRF value. Exploitation requires an authenticated victim to submit the attacker's form, causing deletion with the victim's privileges.
Summary
What happened
Cross-site request forgery in FlyCms 1.0 allows remote attackers to delete a score through a victim's authenticated browser. The /system/score/del endpoint accepts a cross-origin POST containing an attacker-chosen id without a request-bound anti-CSRF value. Exploitation requires an authenticated victim to submit the attacker's form, causing deletion with the victim's privileges.
The record
- CVE
- CVE-2024-22568
- Published
- Jan 18, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- FlyCms score-deletion CSRF formproof 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