p PatchFirst

PatchFirst · Latest vulnerabilities

ibexa/admin-ui vulnerabilities

Vulnerabilities published for ibexa/admin-ui in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 6

  1. GHSA-2mx6-fq24-g2mh

    Medium · CVSS 4.8Fix available

    ibexa/admin-ui has an XSS vulnerability in Cancel/Reschedule future publication modal

    ### 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/sec

    • Update to 4.6.25
    • Update to 5.0.3
    Published Updated
  2. GHSA-5r6x-g6jv-4v87

    Medium · CVSS 6.1Fix available

    Ibexa Admin UI XSS vulnerabilities in back office

    ### Impact This security advisory is a part of IBEXA-SA-2025-003, which resolves XSS vulnerabilities in several parts of the back office of Ibexa DXP. Back office access and varying levels of editing and management permissions are required to exploit these vulnerabilities. This typically means Editor or Administrator role, or similar. Injected XSS is persistent and can 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". - https://github.com/ibexa/admin-ui/commit/72a64d90d249e5f4c4a5e8238f5d627c9b68d9b8 ### W

    • Update to 4.6.21
    Published Updated
  3. CVE-2024-53864

    Medium · CVSS 5.3EPSS 0.53%Fix available

    Cross-site Scripting in a field that is used in the Content name pattern in ibexa/admin-ui

    Ibexa Admin UI Bundle is all the necessary parts to run the Ibexa DXP Back Office interface. The Content name pattern is used to build Content names from one or more fields. An XSS vulnerability has been found in this mechanism. Content edit permission is required to exploit it. After the fix, any existing injected XSS will not run. This issue has been patched in version 4.6.14. All users are advised to upgrade. There are no known workarounds for this vulnerability.

    • Update to 4.6.14
    Published Updated
  4. CVE-2024-39318

    Medium · CVSS 5.4EPSS 0.39%Fix available

    Ibexa Admin UI vulnerable to DOM-based Cross-site Scripting in file upload widget

    The Ibexa Admin UI Bundle contains all the necessary parts to run the Ibexa DXP Back Office interface. The file upload widget is vulnerable to XSS payloads in filenames. Access permission to upload files is required. As such, in most cases only authenticated editors and administrators will have the required permission. It is not persistent, i.e. the payload is only executed during the upload. In effect, an attacker will have to trick an editor/administrator into uploading a strangely named file.

    • Update to 4.6.9
    Published Updated
  5. GHSA-g6jc-xrc3-4wwq

    Not ratedFix available

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

    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.

    • Update to 4.2.3
    Published Updated
  6. GHSA-7644-cxp8-h23r

    Not ratedFix available

    ibexa/admin-ui vulnerable to Cross-site Scripting in content type name/shortname

    Critical severity. It is possible to inject JavaScript XSS in the content type entries "name" and "short name". To exploit this, one must already have permission to edit content types, which limits it in many cases to people who are already administrators. However, please verify which users have this permission. The fix ensures any injections are escaped.

    • Update to 4.2.3
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →