# CVE-2026-33883: Statamic has Reflected XSS via unescaped redirect parameter in its password reset form tag

> Attackers can execute arbitrary JavaScript in victims' browsers via unescaped redirect parameters in the password reset form.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-3jg4-p23x-p4qx

## What is CVE-2026-33883?

CVE-2026-33883 is a medium-severity cross-site scripting vulnerability in statamic cms, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.16 and 6.7.2, the `user:reset_password_form` tag could render user-input directly into HTML without escaping, allowing an attacker to craft a URL that executes arbitrary JavaScript in the victim's browser. This has been fixed in 5.73.16 and 6.7.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-33883?

4 open source packages ship an affected version, including statamic/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | All versions | 5.73.16 |
| `statamic/cms` | Packagist | All versions | 5.73.16 |
| `statamic/cms` | Packagist | From 6.0.0-alpha.1 | 6.7.2 |
| `statamic/cms` | Packagist | From 6.0.0-alpha.1 | 6.7.2 |

Products: Statamic Statamic.

## How do I fix CVE-2026-33883?

Upgrade statamic/cms to a fixed version for your release line: 5.73.16 or 6.7.2.

## Is CVE-2026-33883 being exploited?

There is no known exploitation of CVE-2026-33883 in the wild and no public exploit code.

## Other vulnerabilities in statamic cms

- [CVE-2021-45364](https://insights.sbomify.com/CVE-2021-45364/): Code injection in n/a (critical 9.8)
- [CVE-2026-27593](https://insights.sbomify.com/CVE-2026-27593/): Statamic is vulnerable to account takeover via password reset link injection (critical 9.3)
- [CVE-2026-27939](https://insights.sbomify.com/CVE-2026-27939/): Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass (high 8.8)
- [CVE-2023-48217](https://insights.sbomify.com/CVE-2023-48217/): Remote code execution via form uploads in statamic/cms (high 8.8)
- [CVE-2017-11422](https://insights.sbomify.com/CVE-2017-11422/): Statamic framework Incorrect Permission Assignment (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33883 and fix it if it is affected.

What it is: CVE-2026-33883 is a medium-severity cross-site scripting vulnerability in statamic cms, published on 27 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-33883 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 5.73.16
- statamic/cms (Packagist): affected all versions; fixed in 5.73.16
- statamic/cms (Packagist): affected from 6.0.0-alpha.1; fixed in 6.7.2
- statamic/cms (Packagist): affected from 6.0.0-alpha.1; fixed in 6.7.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33883/ (Markdown: https://insights.sbomify.com/CVE-2026-33883/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33883
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33883
- OSV: https://osv.dev/vulnerability/CVE-2026-33883

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33883/
Summaries are generated and may contain mistakes; the official description above is the record.