CVE-2026-33885
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 versions 5.73.16 and 6.7.2, the external URL detection used for redirect validation on unauthenticated endpoints could be bypassed, allowing users to be redirected to external URLs after actions like form submissions and authentication flows. This has been fixed in 5.73.16 and 6.7.2.
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 confidenceThis is an open redirect vulnerability in Statamic CMS where the external URL detection mechanism used for redirect validation on unauthenticated endpoints can be bypassed. Attackers could potentially redirect users to malicious external websites after form submissions or during authentication flows.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.73.16>= 6.0.0, < 6.7.2CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check installed Statamic versionLocate the composer.json file in the Statamic project root and examine the statamic/cms version constraint, or check the vendor/composer/installed.json file for the installed statamic/cms package versionAffected if The installed version is less than 5.73.16 or greater than or equal to 6.0.0 but less than 6.7.2
-
Identify if unauthenticated redirect endpoints existReview application routes (typically in routes/web.php or Statamic route files) for any endpoints that accept a redirect parameter and are accessible without authenticationAffected if The application has routes that handle redirect parameters on unauthenticated endpoints, particularly those involved in form submissions or authentication flows
-
Inspect redirect configurationExamine the application configuration files (config directory) for any redirect-related settings, particularly those validating external URLs or handling the 'redirect' parameter from requestsAffected if Redirect logic exists that validates external URLs but may allow bypass due to the flawed detection mechanism
A user is affected if they are running Statamic CMS versions below 5.73.16 or between 6.0.0 and 6.7.2 and have unauthenticated endpoints that handle redirect parameters.
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 · scoped5.73.166.7.2
Upgrade Statamic to version 5.73.16 or 6.7.2 or later to patch the vulnerable external URL detection logic.
Statamic 5.73.16+ (for 5.x) or Statamic 6.7.2+ (for 6.x)
- 1. Determine your current Statamic version by checking your composer.json or running `php artisan statamic:version`
- 2. If running Statamic 5.x, upgrade to version 5.73.16 or later by running `composer require statamic/cms:^5.73.16 --update-with-dependencies`
- 3. If running Statamic 6.x, upgrade to version 6.7.2 or later by running `composer require statamic/cms:^6.7.2 --update-with-dependencies`
- 4. Clear the application cache after upgrade with `php artisan cache:clear`
- 5. Test redirect functionality on forms and authentication flows to verify the vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33885 — 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-33885 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