Skip to content
Laskyr

statamic/cms security advisory

CVE-2026-54242: Statamic Vulnerable to Server-Side Request Forgery via Glide (DNS rebinding)

CVE-2026-54242 is a medium-severity SSRF vulnerability in the PHP package statamic/cms (CVSS 4.9), published 17 July 2026. It is fixed in 5.73.24 and 6.20.1, one per release line; earlier versions on each line are affected. Exploiting it needs a low-privilege user account.

medium 4.9 published 2026-07-17 · updated 2026-10-24

Fixed in statamic/cms 5.73.24 and 6.20.1

This SSRF issue affects statamic/cms in 2 release lines: < 5.73.24; >= 6.0.0, < 6.20.1. Upgrade to the fixed version for your release line (5.73.24 and 6.20.1). The newest release, 6.40.0, is not affected.

Affected versions
< 5.73.24
>= 6.0.0, < 6.20.1
Fixed in
5.73.24, 6.20.1
Newest release
6.40.0
Severity
Medium · CVSS 4.9
Type
Server-side request forgery (SSRF)
CWE-367, CWE-918
Exploited in the wild
Not on the CISA KEV list
checked 2026-11-04

Is your statamic/cms version affected?

Run composer show statamic/cms in your project, then enter the version. We check it against this and every other known statamic/cms advisory.

Who can exploit CVE-2026-54242

CVSS vector (scored by GitHub): CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N

Your app is only exposed if it uses the affected part of statamic/cms. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-54242 in statamic/cms

  1. Find the installed version: composer show statamic/cms. If you never required it yourself, composer why statamic/cms shows which package pulls it in.
  2. Update it: composer update statamic/cms --with-all-dependencies. You need the fixed version for your release line (5.73.24 and 6.20.1).
  3. If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "statamic/cms": "^6.20.1" if you can take that version), or upgrade the package that requires it.
  4. Run composer audit. It reads the same advisory data and should no longer list CVE-2026-54242.
  5. Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for SSRF issues while the upgrade waits. None of it replaces the fix.

The CVE-2026-54242 advisory

Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.73.24 and 6.20.1, the Glide image proxy's URL validation in src/Imaging/RemoteUrlValidator.php and src/Imaging/GuzzleAdapter.php could be bypassed using DNS rebinding. The remote hostname was validated as publicly routable, but resolved again when the image was actually fetched, so an attacker controlling the hostname's DNS could rebind it to an internal address after validation and cause the server to make HTTP requests to internal addresses, including loopback, private network, and cloud metadata endpoints. This affects sites that pass user-supplied URLs to Glide. This issue is fixed in versions 5.73.24 and 6.20.1.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-54242. Advisory title: “Statamic Vulnerable to Server-Side Request Forgery via Glide (DNS rebinding)”.

References

Other statamic/cms advisories

Related

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit