# GHSA-8c2g-f8jm-5cr7: ibexa/fieldtype-richtext has an XSS vulnerability via acronym custom tag in Rich Text

> Attackers with editor or admin privileges can inject persistent XSS via the acronym tag, potentially affecting end users in the front office.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Oct 2025

## What is GHSA-8c2g-f8jm-5cr7?

GHSA-8c2g-f8jm-5cr7 is a cross-site scripting vulnerability in ibexa/fieldtype-richtext, published on 17 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

### 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-004-xss-and-enumeration-vulnerabilities-in-back-office

## Which versions are affected by GHSA-8c2g-f8jm-5cr7?

4 open source packages ship an affected version, including ibexa/fieldtype-richtext.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ibexa/fieldtype-richtext` | Packagist | From 4.6.0 | 4.6.25 |
| `ibexa/fieldtype-richtext` | Packagist | From 4.6.0 | 4.6.25 |
| `ibexa/fieldtype-richtext` | Packagist | From 5.0.0 | 5.0.3 |
| `ibexa/fieldtype-richtext` | Packagist | From 5.0.0 | 5.0.3 |

## How do I fix GHSA-8c2g-f8jm-5cr7?

Upgrade ibexa/fieldtype-richtext to a fixed version for your release line: 4.6.25 or 5.0.3.

## Is GHSA-8c2g-f8jm-5cr7 being exploited?

There is no known exploitation of GHSA-8c2g-f8jm-5cr7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8c2g-f8jm-5cr7 and fix it if it is affected.

What it is: GHSA-8c2g-f8jm-5cr7 is a cross-site scripting vulnerability in ibexa/fieldtype-richtext, published on 17 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-8c2g-f8jm-5cr7 in the wild and no public exploit code.

Affected packages and fixed versions:
- ibexa/fieldtype-richtext (Packagist): affected from 4.6.0; fixed in 4.6.25
- ibexa/fieldtype-richtext (Packagist): affected from 4.6.0; fixed in 4.6.25
- ibexa/fieldtype-richtext (Packagist): affected from 5.0.0; fixed in 5.0.3
- ibexa/fieldtype-richtext (Packagist): affected from 5.0.0; fixed in 5.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-8c2g-f8jm-5cr7/ (Markdown: https://insights.sbomify.com/GHSA-8c2g-f8jm-5cr7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8c2g-f8jm-5cr7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8c2g-f8jm-5cr7/
Summaries are generated and may contain mistakes; the official description above is the record.