XSS Vulnerability in ibexa/fieldtype-richtext: Acronym Custom Tag Exploit
Summary
GHSA-8c2g-f8jm-5cr7: ibexa/fieldtype-richtext has an XSS vulnerability via acronym custom tag in Rich Text. Affects ibexa/fieldtype-richtext across 2 version ranges.
>= 4.6.0, < 4.6.25
>= 5.0.0, < 5.0.3
Fixed in 4.6.25 or 5.0.3, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The ibexa/fieldtype-richtext package is a component of the Ibexa DXP (Digital Experience Platform) that allows users to create and manage rich text content in a web application. It provides features for formatting text, embedding media, and utilizing custom tags. However, it has been identified to have a security vulnerability that can be exploited through the acronym custom tag, potentially allowing unauthorized script execution.
Vulnerability Detail
This vulnerability arises from improper handling of user input in the acronym custom tag within the Rich Text editor. An attacker with access to the back office can inject malicious scripts that may persist and affect end users when rendered in the front office. The vulnerability is classified as an XSS (Cross-Site Scripting) issue, which can lead to session hijacking, data theft, or other malicious activities.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 4.6.0, < 4.6.254.6.25composer require ibexa/fieldtype-richtext:4.6.25 -
>= 5.0.0, < 5.0.35.0.3composer require ibexa/fieldtype-richtext:5.0.3
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There are no workarounds available for this vulnerability. The only effective solution is to apply the patches provided in the updated versions of the package.
Conclusion
The ibexa/fieldtype-richtext package has a moderate severity XSS vulnerability that can be exploited through the acronym custom tag. It is crucial to update to the latest patched versions to protect against potential attacks. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for ibexa/fieldtype-richtext →
FAQ
An XSS (Cross-Site Scripting) vulnerability allows attackers to inject malicious scripts into web pages viewed by other users, potentially compromising their data and security.
The vulnerability can be exploited by users with Editor or Administrator roles who have access to the back office of the DXP.
Exploiting this vulnerability can lead to persistent XSS attacks, affecting end users and potentially allowing attackers to steal sensitive information or hijack user sessions.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Unfortunately, there are no workarounds available for this vulnerability. The only solution is to update to the patched versions.
Related vulnerabilities
Recent vulnerabilities recorded for ibexa/fieldtype-richtext.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
