Apache Roller · Cross-Site Request Forgery (CSRF)
Source GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 11 Nov 2026, 16:35 UTC
Thin evidence
One scorer or none| CNA (apache) | CVSS 3.1 | 8.8 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation 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– |
Mavenorg.apache.roller/rollerpkg:maven/org.apache.roller/rollerOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to Apache Roller version 6.1.7 or later, where the vulnerability is fixed by requiring POST requests with valid CSRF tokens for administrative actions that change data. No other mitigations are specified.
Description
Apache Roller versions 5.0.1 through 6.1.6 are vulnerable to a Cross-Site Request Forgery (CSRF) flaw that allows an unauthenticated attacker to create an administrator account. This occurs because the application only enforced request-token checks on POST requests, while administrative actions also accepted GET requests. The vulnerability is addressed in Apache Roller 6.1.7 and later, which require POST requests with a valid token for data-changing actions.