How severe is GHSA-4jjr-vmv7-wh4w?

GHSA-4jjr-vmv7-wh4w has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-4jjr-vmv7-wh4w?

GHSA-4jjr-vmv7-wh4w affects the following packages: statamic/cms (Packagist), statamic/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-4jjr-vmv7-wh4w?

Update statamic/cms to 5.73.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jjr-vmv7-wh4w is resolved across your whole dependency graph.

How do I detect GHSA-4jjr-vmv7-wh4w 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-4jjr-vmv7-wh4w 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-4jjr-vmv7-wh4w?

O3 pinpoints whether GHSA-4jjr-vmv7-wh4w 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-4jjr-vmv7-wh4w actively exploited in the wild?

No public exploit code has been indexed for GHSA-4jjr-vmv7-wh4w 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.

When was GHSA-4jjr-vmv7-wh4w published, and has it been updated?

GHSA-4jjr-vmv7-wh4w was published on April 16, 2026 and was last updated on July 8, 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-4jjr-vmv7-wh4w

HIGH

GHSA-4jjr-vmv7-wh4w is a high-severity (CVSS 8.1) vulnerability in statamic/cms. O3 Security confirms whether GHSA-4jjr-vmv7-wh4w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Statamic: Unsafe method invocation via query value resolution allows data destruction

Also known asCVE-2026-41175

Published

Apr 16, 2026

Updated

Jul 8, 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

Manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets, and user accounts.

The Control Panel requires authentication with minimal permissions in order to exploit. e.g. "view entries" permission to delete entries, or "view users" permission to delete users, etc.

The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resources enabled too.

Sites that enable the REST or GraphQL API without authentication should treat patching as critical priority.

Patches

This has been fixed in 5.73.20 and 6.13.0.

Affected Packages

2 total 2 fixed

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

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.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jjr-vmv7-wh4w 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-4jjr-vmv7-wh4w 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-4jjr-vmv7-wh4w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets, and user accounts. The Control Panel requires authentication with minimal permissions in order to exploit. e.g. "view entries" permission to delete entries, or "view users" permission to delete users, etc. The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resour

O3 Security · Impact-Aware SCA

Is GHSA-4jjr-vmv7-wh4w in your dependencies?

O3 detects GHSA-4jjr-vmv7-wh4w 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