How severe is GHSA-qq2j-9pf8-g58c?

GHSA-qq2j-9pf8-g58c has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qq2j-9pf8-g58c?

GHSA-qq2j-9pf8-g58c affects the following packages: ezsystems/ezpublish-kernel (Packagist), ezsystems/ezplatform-kernel (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qq2j-9pf8-g58c?

Update ezsystems/ezpublish-kernel to 7.5.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qq2j-9pf8-g58c is resolved across your whole dependency graph.

How do I detect GHSA-qq2j-9pf8-g58c in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezpublish-kernel. 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-qq2j-9pf8-g58c 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-qq2j-9pf8-g58c?

O3 pinpoints whether GHSA-qq2j-9pf8-g58c 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-qq2j-9pf8-g58c actively exploited in the wild?

No public exploit code has been indexed for GHSA-qq2j-9pf8-g58c 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-qq2j-9pf8-g58c?

GHSA-qq2j-9pf8-g58c has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 54th 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-qq2j-9pf8-g58c?

GHSA-qq2j-9pf8-g58c is classified as Improper Privilege Management (CWE-269). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qq2j-9pf8-g58c published, and has it been updated?

GHSA-qq2j-9pf8-g58c was published on March 12, 2023 and was last updated on March 4, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-qq2j-9pf8-g58c: ezsystems/ezpublish-kernel (High 7.2)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk54th percentile+0.17%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐘ezsystems/ezpublish-kernel🐘ezsystems/ezplatform-kernel

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

Users with the Company admin role (introduced by the company account feature in v4) can assign any role to any user. This also applies to any other user that has the role / assign policy. Any subtree limitation in place does not have any effect.

The role / assign policy is typically only given to administrators, which limits the scope in most cases, but please verify who has this policy in your installaton. The fix ensures that subtree limitations are working as intended.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezpublish-kernel`	≥ 7.5.0&&< 7.5.30	7.5.30
🐘Packagist	`ezsystems/ezplatform-kernel`	≥ 1.3.0&&< 1.3.26	1.3.26

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

Users with the Company admin role (introduced by the company account feature in v4) can assign any role to any user. This also applies to any other user that has the role / assign policy. Any subtree limitation in place does not have any effect. The role / assign policy is typically only given to administrators, which limits the scope in most cases, but please verify who has this policy in your installaton. The fix ensures that subtree limitations are working as intended.

O3 Security · Impact-Aware SCA

Is GHSA-qq2j-9pf8-g58c in your dependencies?

O3 detects GHSA-qq2j-9pf8-g58c 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

GHSA-qq2j-9pf8-g58c