Is ibexa/fieldtype-richtext vulnerable?

Composer ibexa/fieldtype-richtext has 4 known advisories in the phpwarden feed. Feed 2026.10.29.3, updated 2026-10-29.

4advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2024-43369Persistent Cross-site Scripting in Ibexa RichText Field Typehigh7.2>=4.6.0 and <4.6.104.6.10
GHSA-8c2g-f8jm-5cr7ibexa/fieldtype-richtext has an XSS vulnerability via acronym custom tag in Rich Textmedium0.0>=5.0.0 and <5.0.3 or >=4.6.0 and <4.6.255.0.3, 4.6.25
GHSA-9qv6-4pwm-m68fIbexa RichText Field Type XSS vulnerabilities in back officemedium0.0>=4.6.0-beta1 and <4.6.214.6.21
GHSA-cj3w-g42v-wcj6ibexa/fieldtype-richtext allows access to external entities in XMLhigh0.0>=4.6.0-beta1 and <4.6.194.6.19

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.