# GHSA-g6jc-xrc3-4wwq: Ibexa DXP users with the Company admin role can assign any role to any user

> Users with Company admin role can bypass subtree limitations to assign any role to any user, leading to privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Nov 2022

## What is GHSA-g6jc-xrc3-4wwq?

GHSA-g6jc-xrc3-4wwq is a vulnerability in ibexa/admin-ui, published on 10 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

## Which versions are affected by GHSA-g6jc-xrc3-4wwq?

2 open source packages ship an affected version, including ibexa/admin-ui.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ibexa/admin-ui` | Packagist | From 4.2.0 | 4.2.3 |
| `ibexa/admin-ui` | Packagist | From 4.2.0 | 4.2.3 |

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

Upgrade ibexa/admin-ui to 4.2.3 or later.

## Is GHSA-g6jc-xrc3-4wwq being exploited?

There is no known exploitation of GHSA-g6jc-xrc3-4wwq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g6jc-xrc3-4wwq and fix it if it is affected.

What it is: GHSA-g6jc-xrc3-4wwq is a vulnerability in ibexa/admin-ui, published on 10 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-g6jc-xrc3-4wwq in the wild and no public exploit code.

Affected packages and fixed versions:
- ibexa/admin-ui (Packagist): affected from 4.2.0; fixed in 4.2.3
- ibexa/admin-ui (Packagist): affected from 4.2.0; fixed in 4.2.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-g6jc-xrc3-4wwq/ (Markdown: https://insights.sbomify.com/GHSA-g6jc-xrc3-4wwq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g6jc-xrc3-4wwq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g6jc-xrc3-4wwq/
Summaries are generated and may contain mistakes; the official description above is the record.