How severe is GHSA-jq2f-59pj-p3m3?

No CVSS score has been assigned to GHSA-jq2f-59pj-p3m3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jq2f-59pj-p3m3?

GHSA-jq2f-59pj-p3m3 affects the following packages: craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-jq2f-59pj-p3m3?

Update craftcms/cms to 5.9.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jq2f-59pj-p3m3 is resolved across your whole dependency graph.

How do I detect GHSA-jq2f-59pj-p3m3 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/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-jq2f-59pj-p3m3 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-jq2f-59pj-p3m3?

O3 pinpoints whether GHSA-jq2f-59pj-p3m3 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-jq2f-59pj-p3m3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jq2f-59pj-p3m3 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-jq2f-59pj-p3m3 published, and has it been updated?

GHSA-jq2f-59pj-p3m3 was published on April 14, 2026 and was last updated on May 5, 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-jq2f-59pj-p3m3

Fix: craftcms/cms@b135384

GHSA-jq2f-59pj-p3m3 is a security vulnerability in craftcms/cms. O3 Security confirms whether GHSA-jq2f-59pj-p3m3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Craft CMS has a Missing Authorization Check on User Group Removal via save-permissions Action

Also known asCVE-2026-41128

Published

Apr 14, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐘craftcms/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

Summary

The actionSavePermissions() endpoint allows a user with only viewUsers permission to remove arbitrary users from all user groups. While _saveUserGroups() enforces per-group authorization for additions, it performs no equivalent authorization check for removals, so submitting an empty groups value removes all existing group memberships.

Affected Versions

Craft CMS 5.6.0 through 5.9.14 (latest release at time of report)
Regression introduced in 5.6.0 when the viewUsers permission was added
Prior to 5.6.0, editedUser() required editUsers, which implicitly protected this endpoint
Requires Pro edition or higher (the vulnerable code path is gated by CmsEdition::Pro)

Vulnerability Details

Root Cause

This is a regression introduced in Craft CMS 5.6.0 when the viewUsers permission was added. Before that change, editedUser() required editUsers permission for accessing other users’ data, which implicitly protected actionSavePermissions(). After the change, actionSavePermissions() became reachable for users with read-only access to other users, but the underlying group-saving logic still lacked authorization for group removals.

The vulnerability has two components:

actionSavePermissions() reachable with read-only access: The action only requires a control panel request and delegates to editedUser(), which now only checks viewUsers — a permission explicitly documented as "read-only access to user elements."
Asymmetric authorization in _saveUserGroups(): The method checks assignUserGroup permission only when adding a user to a new group. When the groups parameter is an empty string (resulting in an empty array), the loop is skipped entirely, no authorization checks are run, and all group memberships are removed.

Prerequisites

Attacker has a control panel account with accessCp and viewUsers permissions only
Target user belongs to one or more user groups that grant additional permissions
Pro edition or higher

Attack Steps

Attacker authenticates to the Control Panel
Attacker sends a POST request to actions/users/save-permissions with:
- userId = target user's ID
- groups = `` (empty string)
All group memberships for the target user are removed
All permissions inherited from those groups are immediately revoked

Impact

Privilege revocation: An attacker can strip group-based permissions from arbitrary users, including accounts whose effective access derives from group membership
Denial of access: Users lose access to sections, volumes, and features that were granted through group membership
Bypass of elevated session requirement: Group removal does not trigger requireElevatedSession() (which is only triggered when new groups are added)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 5.6.0&&< 5.9.15	5.9.15

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/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 craftcms/cms to 5.9.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jq2f-59pj-p3m3 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-jq2f-59pj-p3m3 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-jq2f-59pj-p3m3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary The `actionSavePermissions()` endpoint allows a user with only `viewUsers` permission to remove arbitrary users from all user groups. While `_saveUserGroups()` enforces per-group authorization for additions, it performs no equivalent authorization check for removals, so submitting an empty `groups` value removes all existing group memberships. ## Affected Versions - Craft CMS 5.6.0 through 5.9.14 (latest release at time of report) - Regression introduced in 5.6.0 when the `viewUsers` permission was added - Prior to 5.6.0, `editedUser()` required `editUsers`, which implicitly prot

O3 Security · Impact-Aware SCA

Is GHSA-jq2f-59pj-p3m3 in your dependencies?

O3 detects GHSA-jq2f-59pj-p3m3 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