CVE-2026-28423: Statamic Vulnerable to Server-Side Request Forgery via Glide
Impact
When Glide image manipulation is used in insecure mode (which is not the default), the image proxy can be abused by an unauthenticated user to make the server send HTTP requests to arbitrary URLs—either via the URL directly or via the watermark feature. That can allow access to internal services, cloud metadata endpoints, and other hosts reachable from the server.
Patches
This has been fixed in 5.73.11 and 6.4.0.
Other sources
Statmatic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.11 and 6.4.0, when Glide image manipulation is used in insecure mode (which is not the default), the image proxy can be abused by an unauthenticated user to make the server send HTTP requests to arbitrary URLs—either via the URL directly or via the watermark feature. That can allow access to internal services, cloud metadata endpoints, and other hosts reachable from the server. This has been fixed in 5.73.11 and 6.4.0.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-28423?
CVE-2026-28423 is considered a high severity vulnerability due to its potential for Server-Side Request Forgery.
How do I fix CVE-2026-28423?
To fix CVE-2026-28423, upgrade Statamic to version 5.73.11, 6.4.0 or later.
What is the impact of CVE-2026-28423?
The impact of CVE-2026-28423 allows unauthenticated users to exploit the Glide image proxy in insecure mode.
Which versions of Statamic are affected by CVE-2026-28423?
CVE-2026-28423 affects Statamic versions prior to 5.73.11 and 6.4.0.
Is the insecure mode for Glide image manipulation enabled by default in Statamic?
No, the insecure mode for Glide image manipulation is not enabled by default in Statamic.