p PatchFirst

PatchFirst · Latest vulnerabilities

ibexa/fieldtype-richtext vulnerabilities

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

Filter vulnerabilities
Clear filters

Vulnerabilities: 4

  1. GHSA-8c2g-f8jm-5cr7

    Medium · CVSS 4.8Fix available

    ibexa/fieldtype-richtext has an XSS vulnerability via acronym custom tag in Rich Text

    ### Impact This security advisory resolves an XSS vulnerability in acronym custom tag in Rich Text, 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-

    • Update to 4.6.25
    • Update to 5.0.3
    Published Updated
  2. GHSA-9qv6-4pwm-m68f

    Medium · CVSS 6.1Fix available

    Ibexa RichText Field Type 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/fieldtype-richtext/commit/4a4a170c7faa4807ae0f74c581481b835bab3

    • Update to 4.6.21
    Published Updated
  3. GHSA-cj3w-g42v-wcj6

    High · CVSS 7.1Fix available

    ibexa/fieldtype-richtext allows access to external entities in XML

    ### Impact This security advisory resolves a vulnerability in the RichText field type. By entering a maliciously crafted input into the RichText XML, an attacker could perform an attack using XML external entity (XXE) injection, which might be able to read files on the server. To exploit this vulnerability the attacker would need to already have edit permission to content with RichText fields, which typically means Editor role or higher. The fix removes unsafe elements from XML code, while preserving safe elements. If you have a stored XXE attack in your content drafts, the fix prevents it from extracting data both during editing and preview

    • Update to 4.6.19
    Published Updated
  4. CVE-2024-43369

    High · CVSS 7.2EPSS 0.37%Fix available

    Persistent Cross-site Scripting in Ibexa RichText Field Type

    Ibexa RichText Field Type is a Field Type for supporting rich formatted text stored in a structured XML format. In versions on the 4.6 branch prior to 4.6.10, the validator for the RichText fieldtype blocklists `javascript:` and `vbscript:` in links to prevent XSS. This can leave other options open, and the check can be circumvented using upper case. Content editing permissions for RichText content is required to exploit this vulnerability, which typically means Editor role or higher. The fix implements an allowlist instead, which allows only approved link protocols. The new check is case insensitive. Version 4.6.10 contains a patch for this

    • Update to 4.6.10
    Published Updated

Check your server

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

Check your server →