Security readout for executives and security teams
Plain-English summary
CVE-2026-28425 lets a permitted Statamic control panel user potentially run server-side code when Antlers templating is enabled on user-controlled inputs. This can compromise the CMS application, data, and configuration. The issue is serious, but exposure depends on permissions and whether Antlers-enabled fields, form notifications, or addons are in use.
Executive priority
Prioritize patching for any business-critical Statamic site, especially where non-administrator users can access the control panel. The business risk is full application compromise, including sensitive configuration exposure and data modification. Treat this as a high-priority authenticated RCE, not a broad unauthenticated internet worm risk.
Technical view
Statamic CMS before 5.73.16 and 6.x before 6.7.2 is affected by a CWE-94 remote code execution flaw. Exploitation requires authenticated control panel access and relevant permissions to edit or configure Antlers-enabled inputs. Affected paths include explicitly enabled content fields, Forms email notification settings, or third-party addons that add Antlers-enabled fields.
Likely exposure
Internet-facing Statamic sites are most exposed when control panel access is available to multiple users and Antlers runs on editable content or configuration. Sites without Antlers-enabled user-controlled inputs, or with tightly restricted control panel permissions, have lower practical exposure.
Exploitation context
The supplied sources do not show known active exploitation, and the CVE is not marked KEV. This is not an unauthenticated bug; an attacker needs valid control panel access plus the specific permissions needed for the affected Antlers-enabled input path.
Researcher notes
The key exposure question is whether authenticated users can control Antlers-evaluated content. CVSS is 8.0 with low attack complexity, low privileges, required user interaction, and high confidentiality, integrity, and availability impact. Evidence in the supplied sources is sufficient for affected versions and fixed versions, but not for exploitation in the wild.
Mitigation direction
- Update Statamic to 5.73.16 or 6.7.2, as applicable.
- Confirm addon-managed Statamic installations run a patched Statamic version.
- Review and restrict control panel permissions for field configuration and entry editing.
- Identify addons that introduce Antlers-enabled fields and follow their vendor guidance.
- Check Statamic’s security advisory for any updated remediation instructions.
Validation and detection
- Inventory all Statamic installations and record exact CMS versions.
- Verify production versions are 5.73.16, 6.7.2, or later.
- Review content fields where Antlers is explicitly enabled.
- Check Forms email notification settings that support Antlers.
- Review third-party addons, including SEO Pro, for Antlers-enabled fields.
- Audit control panel users with configuration or entry-editing permissions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-28425 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H2.15.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/statamic/cms/security/advisories/GHSA-cpv7-q2wx-m8rwCVE reference · x_refsource_CONFIRM
- https://github.com/statamic/cms/releases/tag/v5.73.11CVE reference · x_refsource_MISC
- https://github.com/statamic/cms/releases/tag/v6.4.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.