CVE-2024-24570: Statamic account takeover via XSS and password reset link

Published Feb 1, 2024
·
Updated

Impact

HTML files crafted to look like jpg files are able to be uploaded, allowing for XSS.

This affects:

- front-end forms with asset fields without any mime type validation - asset fields in the control panel - asset browser in the control panel

Additionally, if the XSS is crafted in a specific way, the "copy password reset link" feature may be exploited to gain access to a user's password reset token and gain access to their account. The authorized user is required to execute the XSS in order for the vulnerability to occur.

Patches

In versions 4.46.0 and 3.4.17, the XSS vulnerability has been patched, and the copy password reset link functionality has been disabled. (Users may still trigger password reset emails.)

Credits

Statamic thanks Niklas Schilling (discovery, analysis, coordination) from the SEC Consult Vulnerability Lab (https://www.sec-consult.com/) for responsibly reporting the identified issues and working with us as we addressed them.

Other sources

Statamic is a Laravel and Git powered CMS. HTML files crafted to look like jpg files are able to be uploaded, allowing for XSS. This affects the front-end forms with asset fields without any mime type validation, asset fields in the control panel, and asset browser in the control panel. Additionally, if the XSS is crafted in a specific way, the "copy password reset link" feature may be exploited to gain access to a user's password reset token and gain access to their account. The authorized user is required to execute the XSS in order for the vulnerability to occur. In versions 4.46.0 and 3.4.17, the XSS vulnerability has been patched, and the copy password reset link functionality has been disabled.

NVD

Affected Software

4 affected componentsFixes available
composer/statamic/cms<3.4.17
3.4.17
composer/statamic/cms>=4.00<4.46.0
4.46.0
Statamic Statamic<3.4.17
Statamic Statamic>=4.0.0<4.46.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/statamic/cms to a version that resolves this vulnerability.

    Fixed in 3.4.17
  2. Upgrade

    Upgrade composer/statamic/cms to a version that resolves this vulnerability.

    Fixed in 4.46.0
  3. Upgrade

    Upgrade Statamic to a version that resolves this vulnerability.

    Fixed in 4.46.0
  4. Upgrade

    Upgrade Statamic to a version that resolves this vulnerability.

    Fixed in 3.4.17

Event History

Feb 1, 2024
CVE Published
via MITRE·04:42 PM
Data Sourced
via MITRE·04:42 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·08:51 PM
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-24570?

CVE-2024-24570 has a moderate severity due to the potential for cross-site scripting (XSS) attacks through improper file uploads.

2

How do I fix CVE-2024-24570?

To fix CVE-2024-24570, update to Statamic CMS version 3.4.17 or 4.46.0 which include necessary security patches.

3

What systems are affected by CVE-2024-24570?

CVE-2024-24570 affects Statamic CMS versions earlier than 3.4.17 and versions from 4.0.0 up to 4.46.0.

4

What kind of attacks can be executed due to CVE-2024-24570?

CVE-2024-24570 can allow attackers to execute cross-site scripting (XSS) attacks by uploading malicious HTML files disguised as image files.

5

Is there a workaround for CVE-2024-24570?

A potential workaround for CVE-2024-24570 is to implement strict MIME type validation for uploaded files in your application.

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