CVE-2026-45660
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStatamic is a Laravel and Git powered content management system (CMS). Prior to 5.73.22 and 6.18.1, the Glide image proxy's URL validation could be bypassed using an IP representation that wasn't normalized before the public-IP check. An unauthenticated user could 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. Sites running PHP 8.3 or newer are not affected. This vulnerability is fixed in 5.73.22 and 6.18.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Glide image proxy in Statamic CMS prior to 5.73.22 and 6.18.1 had an SSRF vulnerability where URL validation could be bypassed using non-normalized IP representations. An unauthenticated attacker could force the server to make HTTP requests to internal addresses including loopback (127.0.0.1), private networks, and cloud metadata endpoints (e.g., AWS169.254.169.254). This affects sites that pass user-supplied URLs to Glide.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Statamic CMS installationLook for Statamic installation by checking for the 'statamic' directory in vendor/composer autoload, or check for 'statamic' in composer.json, or look for the '/!/glide' route pattern in routes configuration.Affected if Statamic CMS is not present, then not affected.
-
Identify installed Statamic versionCheck composer.json for the 'statamic/cms' version number, or run 'php artisan statamic:version' from the application root if artisan is available.Affected if Version is less than 5.73.22 (for Statamic 5.x) or less than 6.18.1 (for Statamic 6.x). Versions prior to these are affected.
-
Check PHP versionRun 'php -v' or check the server PHP version via phpinfo().Affected if PHP version is below 8.3; versions prior to 8.3 are vulnerable. PHP 8.3 and newer are not affected regardless of Statamic version.
-
Verify Glide image proxy is accessibleCheck if the Glide route is enabled by examining routes/web.php or routes.php for the '!/glide' pattern, or attempt to access a route like /!/glide/test.jpg on the site.Affected if Glide proxy is accessible without authentication and routes are not restricted, making exploitation possible.
You are affected if running Statamic CMS with a version below 5.73.22 (v5) or below 6.18.1 (v6), AND running PHP below 8.3, AND the Glide image proxy is publicly accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Statamic to version 5.73.22 or 6.18.1, or ensure PHP 8.3 or newer is running as the vulnerability does not affect PHP 8.3+ environments.
Statamic 5.73.22 (for 5.x users) or 6.18.1 (for 6.x users)
- 1. Determine your current Statamic version by running `php artisan statamic:version` or checking your composer.json
- 2. If you are on Statamic 5.x, upgrade to version 5.73.22
- 3. If you are on Statamic 6.x, upgrade to version 6.18.1
- 4. Run `composer update statamic/cms --with-all-dependencies` to apply the security patch
- 5. Clear any cached configurations with `php artisan cache:clear` and `php artisan config:clear`
- 6. Test the upgrade in a staging environment before deploying to production
- 7. Verify the Glide image proxy functionality works correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45660 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data