CVE-2026-33885
Received Received - Intake
Open Redirect Vulnerability in Statamic CMS External URL Validation

Publication date: 2026-03-27

Last updated on: 2026-04-08

Assigner: GitHub, Inc.

Description
Statamic 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-27
Last Modified
2026-04-08
Generated
2026-05-07
AI Q&A
2026-03-28
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
statamic statamic to 5.73.16 (exc)
statamic statamic From 6.0.0 (inc) to 6.7.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-601 The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-33885 is an open redirect vulnerability in the Statamic content management system versions prior to 5.73.16 and 6.7.2. The issue arises because the external URL detection used for redirect validation on unauthenticated endpoints can be bypassed. This means attackers can trick the system into redirecting users to arbitrary external URLs after actions like form submissions or authentication flows by exploiting differences in how URLs are parsed.

This vulnerability is classified as CWE-601, which involves URL redirection to untrusted sites without proper validation.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability is an open redirect issue that allows attackers to redirect users to arbitrary external URLs after certain actions. While it has low confidentiality and integrity impacts and no availability impact, such open redirect vulnerabilities can potentially be exploited in phishing attacks or to redirect users to malicious sites.

This type of vulnerability may indirectly affect compliance with standards like GDPR or HIPAA by increasing the risk of user data exposure or unauthorized access through social engineering or phishing, but the CVE description does not explicitly state any direct impact on compliance with these regulations.


How can this vulnerability impact me? :

This vulnerability can impact users by allowing attackers to redirect them to malicious external websites after interacting with certain parts of the application, such as submitting forms or completing authentication flows.

  • Attackers can exploit this remotely without needing any privileges.
  • The attack requires user interaction, such as clicking a link or submitting a form.
  • Potential impacts include limited exposure of confidential information and limited integrity impact, but no impact on availability.

Overall, this could lead to phishing attacks or users being redirected to harmful sites, undermining trust in the application.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability is an open redirect issue on unauthenticated endpoints in statamic/cms versions prior to 5.73.16 and 6.7.2. Detection involves identifying if the application improperly redirects users to external URLs after actions such as form submissions or authentication flows.

To detect this on your system, you can test the redirect behavior by sending crafted HTTP requests to the affected endpoints with external URLs as redirect parameters and observe if the application redirects to those external URLs without proper validation.

Example commands using curl to test for open redirect might include:

  • curl -v "http://yourstatamicsite.com/path?redirect=https://malicious.example.com"
  • curl -v "http://yourstatamicsite.com/login?redirect=https://malicious.example.com"

If the response includes a redirect (HTTP 3xx) to the external URL (https://malicious.example.com), the vulnerability is present.


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to upgrade the statamic/cms package to version 5.73.16 or 6.7.2 or later, where this vulnerability has been fixed.

Until the upgrade can be applied, consider implementing temporary measures such as:

  • Review and restrict redirect parameters to only allow internal URLs.
  • Implement web application firewall (WAF) rules to block requests with suspicious redirect parameters pointing to external domains.
  • Monitor logs for unusual redirect activities to external URLs.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart