contao/comments-bundle
Affected
- introduced
4.0.0, fixed5.3.50(ecosystem)
Fixed versions
5.3.50
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-107845
Contao: Cross-site scripting in the comments bundle
An unauthenticated front end visitor can post a comment containing a XSS injection. The victim is any back end user who opens the Comments module, and moderation makes exposure certain rather than preventing it. No Content-Security-Policy header is sent on the Contao back end, so nothing mitigates the inline handler.
Impact
Anyone on the internet can inject script that executes in the Contao back end origin, under the session of whichever user opens the Comments module, with no click and no hover. From there the payload acts as that user through the back end: reading any module they can reach, creating a new administrator, or editing a template, which on Contao is a documented path from back end write access to code execution. Moderation does not help and in fact guarantees exposure, since unpublished comments are still inserted and a moderator has to open the list to act on them.
Critical Basis: The source's own band: CRITICAL
4.0.0, fixed 5.3.50 (ecosystem)5.3.50
The export has no generic command for this ecosystem.
5.4.0-RC1, fixed 5.7.12 (ecosystem)5.7.12
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0