p PatchFirst

PatchFirst · Свежие уязвимости

statamic/cms 6.6.2: известные уязвимости · Страница 2

Известных уязвимостей, затрагивающих statamic/cms 6.6.2: 26. Сравните исправленные версии ниже с установленной у вас.

Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 26

  1. CVE-2026-33882

    Средний · CVSS 6.5EPSS 0,27%Есть исправление

    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.

    • Обновитесь до 6.7.2
    Опубликовано Обновлено
  2. CVE-2026-33177

    Средний · CVSS 4.3EPSS 0,23%Есть исправление

    Statamic is missing authorization check on taxonomy term creation via fieldtype

    Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.14 and 6.7.0, low-privileged Control Panel users could create taxonomy terms by submitting requests to the field action processing endpoint with attacker-controlled field definitions. This bypasses the authorization checks enforced on the standard taxonomy term creation endpoint. This has been fixed in 5.73.14 and 6.7.0.

    • Обновитесь до 6.7.0
    Опубликовано Обновлено
  3. CVE-2026-33172

    Высокий · CVSS 8.7EPSS 0,33%Есть исправление

    Statamic has Stored XSS via SVG Sanitization Bypass

    Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.14 and 6.7.0, a stored XSS vulnerability in SVG asset reuploads allows authenticated users with asset upload permissions to bypass SVG sanitization and inject malicious JavaScript that executes when the asset is viewed. This has been fixed in 5.73.14 and 6.7.0.

    • Обновитесь до 6.7.0
    Опубликовано Обновлено
  4. CVE-2026-33171

    Средний · CVSS 4.3EPSS 0,36%Есть исправление

    Statamic has a path traversal in file dictionary fieldtype

    Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.14 and 6.7.0, authenticated Control Panel users could read arbitrary `.json`, `.yaml`, and `.csv` files from the server by manipulating the file dictionary's `filename` configuration parameter in the fieldtype's endpoint. This has been fixed in 5.73.14 and 6.7.0.

    • Обновитесь до 6.7.0
    Опубликовано Обновлено
  5. CVE-2026-28425

    Высокий · CVSS 8.0EPSS 0,5%Есть исправление

    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

    • Обновитесь до 6.7.2
    Опубликовано Обновлено
  6. CVE-2026-27593

    Критический · CVSS 9.3EPSS 0,52%Есть исправление

    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.

    • Обновитесь до 6.7.1
    Опубликовано Обновлено

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →