CVE-2024-22591: CSRF
First published: Thu Jan 18 2024(Updated: )
FlyCms v1.0 contains a Cross-Site Request Forgery (CSRF) vulnerability via /system/user/group_save.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| FlyCms | =1.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-22591?
The severity of CVE-2024-22591 is considered to be high due to the potential for exploit via Cross-Site Request Forgery.
How do I fix CVE-2024-22591?
To fix CVE-2024-22591, ensure that CSRF tokens are implemented and validated for all state-changing requests in FlyCms.
What versions of FlyCms are affected by CVE-2024-22591?
CVE-2024-22591 affects FlyCms version 1.0.
Can CVE-2024-22591 lead to unauthorized actions?
Yes, CVE-2024-22591 can allow attackers to perform unauthorized actions on behalf of authenticated users.
Is there a workaround for CVE-2024-22591?
Currently, implementing CSRF protection mechanisms is the recommended workaround for CVE-2024-22591.
- agent/references
- agent/type
- agent/first-publish-date
- agent/description
- agent/author
- agent/event
- agent/severity
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/last-modified-date
- agent/softwarecombine
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/flycms project
- canonical/flycms
- version/flycms/1.0