Skip to content

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

High severity GitHub Reviewed Published Feb 1, 2024 in statamic/cms • Updated Feb 14, 2024

Package

composer statamic/cms (Composer)

Affected versions

>= 4.00, < 4.46.0
< 3.4.17

Patched versions

4.46.0
3.4.17

Description

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.

References

@jasonvarga jasonvarga published to statamic/cms Feb 1, 2024
Published by the National Vulnerability Database Feb 1, 2024
Published to the GitHub Advisory Database Feb 1, 2024
Reviewed Feb 1, 2024
Last updated Feb 14, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

EPSS score

0.052%
(22nd percentile)

CVE ID

CVE-2024-24570

GHSA ID

GHSA-vqxq-hvxw-9mv9

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.