Skip to content
Connect AISign inSign up free
CVE-2026-284258.0HighCWE-94

CVE-2026-28425: Statamic vulnerable to remote code execution via Antlers-enabled control panel inputs

statamic · cms

Affected: statamic cms · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.5%probability of exploitation in the next 30 days
43rd percentile
050100

Higher than 43% of scored CVEs

8.0HighCVSS 3.1
LowHigh

DescriptionCVE.org

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 supports Antlers such as Forms email notification settings (requiring configuration permission), or third-party addons that add Antlers-enabled fields to entries (for example, the SEO Pro addon). In each case the attacker must have the relevant control panel permissions. This has been fixed in 5.73.16 and 6.7.2. Users of addons that depend on Statamic should ensure that after updating they are running a patched Statamic version.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • statamic · cms< 5.73.16; >= 6.0.0, < 6.7.2

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
statamic
Published
February 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-28425 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References