How severe is GHSA-g6jc-xrc3-4wwq?

No CVSS score has been assigned to GHSA-g6jc-xrc3-4wwq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g6jc-xrc3-4wwq?

GHSA-g6jc-xrc3-4wwq affects the following packages: ibexa/admin-ui (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-g6jc-xrc3-4wwq?

Update ibexa/admin-ui to 4.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g6jc-xrc3-4wwq is resolved across your whole dependency graph.

How do I detect GHSA-g6jc-xrc3-4wwq in my Packagist dependencies?

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

How do I mitigate GHSA-g6jc-xrc3-4wwq 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-g6jc-xrc3-4wwq?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g6jc-xrc3-4wwq can be triaged on real exposure rather than presence alone.

Is GHSA-g6jc-xrc3-4wwq actively exploited in the wild?

No public exploit code has been indexed for GHSA-g6jc-xrc3-4wwq 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-g6jc-xrc3-4wwq published, and has it been updated?

GHSA-g6jc-xrc3-4wwq was published on November 10, 2022 and was last updated on December 2, 2024. 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-g6jc-xrc3-4wwq — ibexa/admin-ui

Fix: ibexa/admin-ui@e34abb0

GHSA-g6jc-xrc3-4wwq is a security vulnerability in ibexa/admin-ui. A fix is available for ibexa/admin-ui — see the affected versions and patch details below.

Ibexa DXP users with the Company admin role can assign any role to any user

Published

Nov 10, 2022

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘ibexa/admin-ui

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

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ibexa/admin-ui`	≥ 4.2.0&&< 4.2.3	4.2.3`composer require ibexa/admin-ui:^4.2.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/admin-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibexa/admin-ui to 4.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g6jc-xrc3-4wwq 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g6jc-xrc3-4wwq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g6jc-xrc3-4wwq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Critical severity. 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-g6jc-xrc3-4wwq in your dependencies?

O3 Security finds GHSA-g6jc-xrc3-4wwq across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works