How severe is GHSA-3jg4-p23x-p4qx?

GHSA-3jg4-p23x-p4qx has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-3jg4-p23x-p4qx?

GHSA-3jg4-p23x-p4qx affects the following packages: statamic/cms (Packagist), statamic/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-3jg4-p23x-p4qx?

Update statamic/cms to 5.73.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jg4-p23x-p4qx is resolved across your whole dependency graph.

How do I detect GHSA-3jg4-p23x-p4qx in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for statamic/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3jg4-p23x-p4qx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3jg4-p23x-p4qx?

O3 pinpoints whether GHSA-3jg4-p23x-p4qx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3jg4-p23x-p4qx actively exploited in the wild?

No public exploit code has been indexed for GHSA-3jg4-p23x-p4qx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-3jg4-p23x-p4qx?

GHSA-3jg4-p23x-p4qx is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-3jg4-p23x-p4qx published, and has it been updated?

GHSA-3jg4-p23x-p4qx was published on March 26, 2026 and was last updated on March 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-3jg4-p23x-p4qx

MEDIUM

GHSA-3jg4-p23x-p4qx is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in statamic/cms. O3 Security confirms whether GHSA-3jg4-p23x-p4qx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Statamic has Reflected XSS via unescaped redirect parameter in its password reset form tag

Also known asCVE-2026-33883

Published

Mar 26, 2026

Updated

Mar 27, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐘statamic/cms🐘statamic/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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.

Patches

This has been fixed in 5.73.16 and 6.7.2.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`statamic/cms`	all versions	5.73.16
🐘Packagist	`statamic/cms`	≥ 6.0.0-alpha.1&&< 6.7.2	6.7.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for statamic/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update statamic/cms to 5.73.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jg4-p23x-p4qx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3jg4-p23x-p4qx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3jg4-p23x-p4qx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact 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. ### Patches This has been fixed in 5.73.16 and 6.7.2.

O3 Security · Impact-Aware SCA

Is GHSA-3jg4-p23x-p4qx in your dependencies?

O3 detects GHSA-3jg4-p23x-p4qx across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works