CVE-2024-22817: CSRF
Published Jan 18, 2024
·Updated
FlyCms v1.0 contains a Cross-Site Request Forgery (CSRF) vulnerability via /system/email/emailconfupdagte
Affected Software
1 affected component
Flycms Project Flycms=1.0
Event History
Jan 18, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-22817?
CVE-2024-22817 is classified as a high-severity Cross-Site Request Forgery (CSRF) vulnerability.
2
How do I fix CVE-2024-22817?
To fix CVE-2024-22817, you should implement anti-CSRF tokens in the affected functionality and update to a patched version of FlyCms.
3
What versions of FlyCms are affected by CVE-2024-22817?
CVE-2024-22817 affects FlyCms version 1.0.
4
What is the impact of CVE-2024-22817 on my application?
The impact of CVE-2024-22817 allows attackers to perform unauthorized actions on behalf of authenticated users due to the CSRF vulnerability.
5
How can I verify if my installation is vulnerable to CVE-2024-22817?
You can verify your installation by checking if it allows unauthenticated requests to the /system/email/email_conf_update endpoint without proper CSRF protection.