Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-qq2j-9pf8-g58c

HIGHFix: ezsystems/ezpublish-kernel@957e67a

GHSA-qq2j-9pf8-g58c is a high-severity (CVSS 7.2) Improper Privilege Management vulnerability in ezsystems/ezpublish-kernel. O3 Security confirms whether GHSA-qq2j-9pf8-g58c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Company admin role gives excessive privileges in eZ Platform Ibexa

Also known asCVE-2022-48365
Published
Mar 12, 2023
Updated
Mar 4, 2025
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Real-World Exposure

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
EcosystemPackageVulnerable rangeFix
🐘Packagistezsystems/ezpublish-kernel7.5.0&&< 7.5.307.5.30
🐘Packagistezsystems/ezplatform-kernel1.3.0&&< 1.3.261.3.26

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. 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.

  3. 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.

  4. 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.