CVE-2024-22591: CSRF

Published Jan 18, 2024
·
Updated

FlyCms v1.0 contains a Cross-Site Request Forgery (CSRF) vulnerability via /system/user/groupsave.

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·03:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

What versions of FlyCms are affected by CVE-2024-22591?

CVE-2024-22591 affects FlyCms version 1.0.

4

Can CVE-2024-22591 lead to unauthorized actions?

Yes, CVE-2024-22591 can allow attackers to perform unauthorized actions on behalf of authenticated users.

5

Is there a workaround for CVE-2024-22591?

Currently, implementing CSRF protection mechanisms is the recommended workaround for CVE-2024-22591.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203