Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-91204 Overview
CVE-2026-91204 is a stored cross-site scripting (XSS) vulnerability in Apache Roller 6.1.5. An anonymous remote attacker can submit a blog comment containing a javascript: URI that survives the application's HTML comment formatting routine. When a visitor clicks the resulting link, the attacker-controlled script executes in the visitor's browser context.
The flaw affects only Roller instances that enable HTML in comments (users.comments.htmlenabled=true) and use the HTMLSubset comment formatter. Comment moderation, where enabled, delays but does not prevent publication. The weakness is classified as [CWE-79].
Critical Impact
Stored XSS in blog comments allows anonymous attackers to execute arbitrary JavaScript in visitors' browsers, enabling session hijacking, credential theft, and defacement in administrator contexts.
Affected Products
- Apache Roller 6.1.5
- Apache Roller configurations with users.comments.htmlenabled=true
- Apache Roller instances using the HTMLSubset comment formatter
Discovery Timeline
- 2026-09-28 - CVE-2026-91204 published to NVD
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-91204
Vulnerability Analysis
Apache Roller permits a restricted subset of HTML in user comments when the HTMLSubset formatter is enabled. The sanitizer removes most dangerous constructs but reconstructs anchor tags and preserves their href attributes. The reconstruction logic in version 6.1.5 does not restrict the URI scheme of the restored link.
An attacker submits a comment containing an anchor whose href uses the javascript: scheme. The sanitizer accepts the link, strips surrounding markup it does not recognize, and emits the anchor into the rendered page. When a reader clicks the link, the browser executes the attacker's script under the Roller site's origin.
The vulnerability requires user interaction (UI:R) because exploitation depends on a visitor clicking the malicious link. The scope change (S:C) reflects that the executed script runs in the context of any authenticated user who clicks, including administrators.
Root Cause
The comment formatting routine performs allowlist-based tag reconstruction but does not validate the URI scheme of href attributes. Any scheme including javascript:, data:, or vbscript: passes through the filter unchanged. The patch in 6.1.6 restricts restored links to http, https, and mailto URIs.
Attack Vector
Exploitation requires a vulnerable Roller instance with HTML comments enabled and the HTMLSubset formatter in use. The attacker posts a comment through the public comment form. On sites with moderation, publication is delayed until an administrator approves the comment, but the payload persists intact. Once published, the stored link executes JavaScript for every visitor who clicks it.
The vulnerability is described in prose because no public proof-of-concept exploit is available. Technical remediation details are documented in the Apache Roller Pull Request #190 and the Apache mailing list disclosure.
Detection Methods for CVE-2026-91204
Indicators of Compromise
- Comment records in the Roller database containing anchor tags with href values beginning with javascript:, data:, or vbscript:.
- Web server access logs showing POST requests to the comment submission endpoint followed by clicks on anchor links in rendered comment pages.
- Unexpected outbound requests from authenticated administrator sessions to attacker-controlled domains referenced from comment pages.
Detection Strategies
- Query the Roller comment store for the literal substring javascript: within comment body fields.
- Inspect rendered blog pages with an automated crawler that flags anchor elements whose href attribute uses non-standard URI schemes.
- Review comment moderation queues for links that render identically to safe URLs but encode script payloads in the scheme.
Monitoring Recommendations
- Enable comment moderation and audit the moderation queue before approving external links.
- Instrument the Roller application to log all href scheme values written to comment records.
- Monitor administrator session activity for anomalous XHR requests or token exfiltration patterns following comment-page navigation.
How to Mitigate CVE-2026-91204
Immediate Actions Required
- Upgrade Apache Roller to version 6.1.6 or later, which restricts restored anchor links to http, https, and mailto schemes.
- Audit existing comment data for stored payloads containing non-standard URI schemes and remove or rewrite them.
- Enable comment moderation on all Roller sites that currently publish anonymous comments without review.
Patch Information
The fix is included in Apache Roller 6.1.6. The patch restricts the set of URI schemes permitted in reconstructed anchor href attributes to http, https, and mailto. Review the upstream pull request for the exact code changes and the Openwall OSS Security announcement for the vendor advisory.
Workarounds
- Set users.comments.htmlenabled=false in the Roller configuration to disable HTML parsing in comments entirely.
- Switch the comment formatter away from HTMLSubset to a plaintext-only formatter until the upgrade is applied.
- Require comment moderation and reject any submission containing anchor tags with non-http(s) or non-mailto schemes.
# Disable HTML in comments as a temporary mitigation
# Edit roller-custom.properties and set:
users.comments.htmlenabled=false
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

