How severe is GHSA-g7xp-jf3x-wcx4?

No CVSS score has been assigned to GHSA-g7xp-jf3x-wcx4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g7xp-jf3x-wcx4?

GHSA-g7xp-jf3x-wcx4 affects the following packages: concrete5/concrete5 (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-g7xp-jf3x-wcx4?

Update concrete5/concrete5 to 9.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7xp-jf3x-wcx4 is resolved across your whole dependency graph.

How do I detect GHSA-g7xp-jf3x-wcx4 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for concrete5/concrete5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g7xp-jf3x-wcx4 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is GHSA-g7xp-jf3x-wcx4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g7xp-jf3x-wcx4 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 is the EPSS score for GHSA-g7xp-jf3x-wcx4?

GHSA-g7xp-jf3x-wcx4 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g7xp-jf3x-wcx4?

GHSA-g7xp-jf3x-wcx4 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g7xp-jf3x-wcx4 published, and has it been updated?

GHSA-g7xp-jf3x-wcx4 was published on May 21, 2026 and was last updated on September 10, 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

Not in CISA KEV

GHSA-g7xp-jf3x-wcx4 — concrete5/concrete5

GHSA-g7xp-jf3x-wcx4 is a CWE-863 vulnerability in concrete5/concrete5. A fix is available for concrete5/concrete5 — see the affected versions and patch details below.

Concrete CMS is vulnerable to missing authorization in the bulk_user_assignment.php

Also known asCVE-2026-8350

Published

May 21, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g7xp-jf3x-wcx4.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘concrete5/concrete5

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

Concrete CMS 9.5.0 and below is vulnerable to missing authorization in the bulk_user_assignment.php which can lead to privilege escalation to Administrative Group. Any authenticated user with access to the bulk user assignment dashboard page can add any user email to any group and can remove legitimate admins. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 7.5 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Thanks Vincent55 for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`concrete5/concrete5`	all versions	9.5.1`composer require concrete5/concrete5:^9.5.1`

Affected Products

1 product · 1 configurations

Application

concrete cmsconcretecms

≤ 9.5.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for concrete5/concrete5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update concrete5/concrete5 to 9.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7xp-jf3x-wcx4 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-g7xp-jf3x-wcx4 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works