Task modification via forged edit requests
Published Jan 16, 2025 · Updated Jan 31, 2025
Cross-site request forgery in 07FLYCMS 1.3.9 allows remote attackers to modify task records through a victim's browser. The OaTask edit endpoint accepts a cross-origin POST containing the task ID, owner, schedule, status, and content fields without a request-integrity token. Exploitation requires a logged-in user to submit an attacker-controlled form, and the resulting request changes the selected task.
Summary
What happened
Cross-site request forgery in 07FLYCMS 1.3.9 allows remote attackers to modify task records through a victim's browser. The OaTask edit endpoint accepts a cross-origin POST containing the task ID, owner, schedule, status, and content fields without a request-integrity token. Exploitation requires a logged-in user to submit an attacker-controlled form, and the resulting request changes the selected task.
The record
- CVE
- CVE-2024-57160
- Published
- Jan 16, 2025
- Updated
- Jan 31, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2025CVE publishedPublication date reported by the CVE source.
- Jan 31, 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
- OaTask edit CSRF proof-of-concept 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