CVE-2024-24570

Statmic CMS vulnerable to account takeover via XSS and password reset link

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.

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-24570 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.46.0, 3.4.17); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.)

1. What is CVE-2024-24570? CVE-2024-24570 is a high-severity cross-site scripting (XSS) vulnerability in statamic/cms (composer), affecting versions >= 4.00, < 4.46.0. It is fixed in 4.46.0, 3.4.17. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-24570? CVE-2024-24570 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of statamic/cms are affected by CVE-2024-24570? statamic/cms (composer) versions >= 4.00, < 4.46.0 is affected.
4. Is there a fix for CVE-2024-24570? Yes. CVE-2024-24570 is fixed in 4.46.0, 3.4.17. Upgrade to this version or later.
5. Is CVE-2024-24570 exploitable, and should I be worried? Whether CVE-2024-24570 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-24570 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-24570?
   • Upgrade statamic/cms to 4.46.0 or later
   • Upgrade statamic/cms to 3.4.17 or later

Other vulnerabilities in statamic/cms