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

GHSA-2mx6-fq24-g2mh — ibexa/admin-ui

GHSA-2mx6-fq24-g2mh 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/admin-ui has an XSS vulnerability in Cancel/Reschedule future publication modal

Published
Oct 17, 2025
Updated
Oct 17, 2025
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 17, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐘ibexa/admin-ui🐘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

Impact

This security advisory resolves an XSS vulnerability in image asset names, content language names and future publishing in the back office of the DXP. Back office access and varying levels of editing and management permissions are required to exploit this vulnerability. This typically means Editor or Administrator role, or similar. Injected XSS is persistent and may in some cases be reflected in the front office, possibly affecting end users. The fixes ensure XSS is escaped, and any existing injected XSS is rendered harmless.

Patches

See "Patched versions".

Workarounds

None.

References

https://developers.ibexa.co/security-advisories/ibexa-sa-2025-004-xss-and-enumeration-vulnerabilities-in-back-office

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistibexa/admin-ui≥ 5.0.0&&< 5.0.35.0.3composer require ibexa/admin-ui:^5.0.3
🐘Packagistibexa/admin-ui≥ 4.6.0&&< 4.6.254.6.25composer require ibexa/admin-ui:^4.6.25

Detection & mitigation playbook

Open-source dependency

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

  2. Fix

    Update ibexa/admin-ui to 5.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2mx6-fq24-g2mh 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2mx6-fq24-g2mh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2mx6-fq24-g2mh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact This security advisory resolves an XSS vulnerability in image asset names, content language names and future publishing in the back office of the DXP. Back office access and varying levels of editing and management permissions are required to exploit this vulnerability. This typically means Editor or Administrator role, or similar. Injected XSS is persistent and may in some cases be reflected in the front office, possibly affecting end users. The fixes ensure XSS is escaped, and any existing injected XSS is rendered harmless. ### Patches See "Patched versions". ### Workarounds Non
O3 Security · Impact-Aware SCA

Is GHSA-2mx6-fq24-g2mh in your dependencies?

O3 Security finds GHSA-2mx6-fq24-g2mh 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
GHSA-2mx6-fq24-g2mh: ibexa/admin-ui XSS | O3 Security