XSS in richtext custom tag attributes in ezsystems/ezplatform-richtext
Impact
The rich text editor does not escape attribute data when previewing custom tags. This means XSS is possible if custom tags are used, for users who have access to editing rich text content. Frontend content view is not affected, but the vulnerability could be used by editors to attack other editors. The fix ensures custom tag attribute data is escaped in the editor.
Source excerpt · OSVAffected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| From 2.3.0 before 2.3.7.1Ecosystem versions | 2.3.7.1 |
Version evidence: OSV · GHSA-fxwm-rx68-p5vx
View original version evidence (8 explicit versions)
Original source description
The rich text editor does not escape attribute data when previewing custom tags. This means XSS is possible if custom tags are used, for users who have access to editing rich text content. Frontend content view is not affected, but the vulnerability could be used by editors to attack other editors. The fix ensures custom tag attribute data is escaped in the editor.
References
- Security advisory github.com/ezsystems/ezplatform-richtext/security/advisories/GHSA-fxwm-rx68-p5vx
- Patch github.com/ezsystems/ezplatform-richtext/commit/3cebfe2ae4c22e6590632a0ff71893854a16afc5
- Security advisory developers.ibexa.co/security-advisories/ibexa-sa-2021-010-xss-in-richtext-custom-tag-attributes
- Source reference github.com/ezsystems/ezplatform-richtext