p PatchFirst

PatchFirst · Latest vulnerabilities

statamic/cms 6.7.0: known vulnerabilities · Page 2

Known vulnerabilities affecting statamic/cms 6.7.0: 23. Compare the fixes below with your installed release.

Filter vulnerabilities
Clear filters

Vulnerabilities: 23

  1. CVE-2026-33882

    Medium · CVSS 6.5EPSS 0.27%Fix available

    Statamic's Markdown preview endpoint exposes sensitive user data

    Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.16 and 6.7.2, the markdown preview endpoint could be manipulated to return augmented data from arbitrary fieldtypes. With the users fieldtype specifically, an authenticated control panel user could retrieve sensitive user data including email addresses, encrypted passkey data, and encrypted two-factor authentication codes. This has been fixed in 5.73.16 and 6.7.2.

    • Update to 6.7.2
    Published Updated
  2. CVE-2026-28425

    High · CVSS 8.0EPSS 0.5%Fix available

    Statamic vulnerable to remote code execution via Antlers-enabled control panel inputs

    Statmatic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.16 and 6.7.2, an authenticated control panel user with access to Antlers-enabled inputs may be able to achieve remote code execution in the application context. That can lead to full compromise of the application, including access to sensitive configuration, modification or exfiltration of data, and potential impact on availability. Exploitation is only possible where Antlers runs on user-controlled content—for example, content fields with Antlers explicitly enabled (requiring permission to configure fields and to edit entries), built-in config that

    • Update to 6.7.2
    Published Updated
  3. CVE-2026-27593

    Critical · CVSS 9.3EPSS 0.52%Fix available

    Statamic is vulnerable to account takeover via password reset link injection

    Statmatic is a Laravel and Git powered content management system (CMS). Prior to versions 6.3.3 and 5.73.10, an attacker may leverage a vulnerability in the password reset feature to capture a user's token and reset the password on their behalf. The attacker must know the email address of a valid account on the site, and the actual user must blindly click the link in their email even though they didn't request the reset. This has been fixed in 6.3.3 and 5.73.10.

    • Update to 6.7.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →