Unauthorized group changes via tokenless cross-origin POST
Published Jan 18, 2024 · Updated Jun 20, 2025
CSRF in FlyCms 1.0 allows remote attackers to submit unauthorized user-group changes through /system/user/group_save. The group_save handler accepts a cross-origin POST containing groupName and group-policy fields without a request-bound anti-CSRF token. Exploitation requires a victim browser carrying an authorized FlyCms session to load attacker-controlled content, causing the browser to create or alter a group with the submitted values.
Summary
What happened
CSRF in FlyCms 1.0 allows remote attackers to submit unauthorized user-group changes through /system/user/group_save. The group_save handler accepts a cross-origin POST containing groupName and group-policy fields without a request-bound anti-CSRF token. Exploitation requires a victim browser carrying an authorized FlyCms session to load attacker-controlled content, causing the browser to create or alter a group with the submitted values.
The record
- CVE
- CVE-2024-22591
- Published
- Jan 18, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352
- 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
- HTML CSRF form for group_saveproof of concept · unverified
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