Apache Roller · Cross-site Scripting
Source GCVE Database
Not known to be exploited · fixed in 6.1.7 : patch Apache Roller soon.
Data as of 11 Nov 2026, 17:03 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 6.1.7
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Roller | Affected
| Fixed in– |
AI-suggested
Users should upgrade to Apache Roller version 6.1.7 or later, which removes HTML characters from tag names and sanitizes previously stored tags. Since AtomPub is disabled by default, ensuring it remains disabled reduces exposure. Additionally, the default setting weblogAdminsUntrusted=true since 6.1.4 helps mitigate risk by treating authors as untrusted. No other specific mitigations are indicated.
Description
Apache Roller versions 5.0.1 through 6.1.6 contain a cross-site scripting (XSS) vulnerability that allows authenticated users with the Author role to inject script via entry tags submitted through AtomPub. The vulnerability arises because Roller’s tag filter permits HTML characters in tag names, and certain themes and macros render these tags without escaping, enabling script execution in viewers' browsers. AtomPub is disabled by default, and since version 6.1.4, the default setting assumes weblog authors are untrusted. Upgrading to version 6.1.7 or later mitigates this issue by removing HTML characters from tag names, including previously stored ones.