Unauthorized state changes via self-generated CSRF salt
Published Sep 28, 2026 · Updated Sep 28, 2026
Cross-site request forgery in Apache Roller 6.1.5 allows remote attackers to make logged-in users perform unauthorized state-changing actions. The salt-validation filters accept a request without a submitted salt by checking a value generated by the server for that request; multipart forms also lack the same submitted-salt check. Exploitation requires an author or administrator to visit a crafted page, and the resulting actions are limited to that user's authority.
Summary
What happened
Cross-site request forgery in Apache Roller 6.1.5 allows remote attackers to make logged-in users perform unauthorized state-changing actions. The salt-validation filters accept a request without a submitted salt by checking a value generated by the server for that request; multipart forms also lack the same submitted-salt check. Exploitation requires an author or administrator to visit a crafted page, and the resulting actions are limited to that user's authority.
The record
- CVE
- CVE-2026-82380
- Published
- Sep 28, 2026
- Updated
- Sep 28, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Roller
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 2026CVE publishedPublication date reported by the CVE source.
- Sep 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.1.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started