Security readout for executives and security teams
Plain-English summary
Statamic CMS sites using Glide image manipulation in insecure mode can be tricked into making server-side web requests. This matters because the server may reach internal systems or cloud metadata services that are not exposed to the internet. The insecure mode is not the default, reducing likely exposure.
Executive priority
Treat as a targeted configuration-dependent issue. Prioritize public Statamic sites, especially those hosted in cloud environments or networks with sensitive internal services. Upgrade during the next security maintenance window, sooner if insecure Glide mode is confirmed.
Technical view
CVE-2026-28423 is an unauthenticated SSRF in Statamic CMS before 5.73.11 and in 6.x before 6.4.0. When Glide is configured in insecure mode, the image proxy can request arbitrary URLs directly or through the watermark feature. Impact is primarily confidentiality, with high attack complexity and changed scope per CVSS 3.1 score 6.8.
Likely exposure
Exposure is limited to Statamic CMS installations running affected versions with Glide image manipulation enabled in insecure mode. Default configurations are reportedly not affected. Internet-facing CMS deployments have higher concern if their servers can reach internal networks or cloud metadata endpoints.
Exploitation context
The sources do not report active exploitation, and this CVE is not listed as KEV in the provided bundle. Exploitation requires a specific insecure Glide configuration, but no authentication or user interaction is required once that condition exists.
Researcher notes
The advisory identifies SSRF through Glide’s image proxy and watermark handling only when insecure mode is used. The provided sources do not include proof-of-concept details or evidence of exploitation. Validation should focus on version, Glide configuration, and reachable internal assets rather than broad Statamic exposure.
Mitigation direction
- Upgrade Statamic 5.x to 5.73.11 or later.
- Upgrade Statamic 6.x to 6.4.0 or later.
- Review Glide configuration and avoid insecure mode unless vendor guidance explicitly supports it.
- Restrict server egress to internal services and cloud metadata endpoints where feasible.
- Monitor vendor advisory updates for additional guidance.
Validation and detection
- Inventory Statamic CMS instances and record installed versions.
- Check whether Glide image manipulation is enabled.
- Confirm whether Glide is configured in insecure mode.
- Verify affected instances have been upgraded to fixed versions.
- Review web and application logs for unusual image proxy URL usage.
- Assess server network reachability to sensitive internal services.
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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-28423 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
- Medium
- CVSS
- 6.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
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:H/PR:N/UI:N/S:C/C:H/I:N/A:N2.24Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/statamic/cms/security/advisories/GHSA-cwpp-325q-2cvpCVE 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.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.