Skip to content
OpenAdvisories

Package · Packagist

ibexa/admin-ui

6 known vulnerabilities.

6 results · Feed

  • Medium —

    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 explo…

  • Medium —

    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 vu…

  • Medium 5.3

    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 req…

  • Medium 5.4

    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 …

  • Critical —

    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 ef…

  • Critical —

    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. Ho…