Score-rule modification via forged authenticated request
Published Jan 18, 2024 · Updated Jun 20, 2025
Cross-site request forgery in FlyCms 1.0 allows remote attackers to alter score rules through /system/score/scorerule_save. The published proof uses an auto-submitted cross-origin POST with name, score, remark, type, and status fields, which the endpoint accepts as the signed-in user. Exploitation requires an authenticated FlyCms user to load attacker-controlled HTML, causing the browser to send the forged state-changing request with that user's session.
Summary
What happened
Cross-site request forgery in FlyCms 1.0 allows remote attackers to alter score rules through /system/score/scorerule_save. The published proof uses an auto-submitted cross-origin POST with name, score, remark, type, and status fields, which the endpoint accepts as the signed-in user. Exploitation requires an authenticated FlyCms user to load attacker-controlled HTML, causing the browser to send the forged state-changing request with that user's session.
The record
- CVE
- CVE-2024-22601
- 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.
Weakness, pattern, technique
Public exploit references
- Auto-submitted score-rule CSRF proofproof 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