Apache Roller: Server-side request forgery (CVE-2026-82375)
Apache Roller 6.1.5 allows an authenticated user with entry-editing rights to perform SSRF attacks by triggering legacy outbound Trackback or entry enclosure handling to arbitrary destinations.
CVE search metadata
CVE search record: CVE-2026-82375. Severity: high. CVSS: 7.4. EPSS: 0.29%. KEV: no. Product: Apache Roller. Brief: Apache Roller: Server-side request forgery (CVE-2026-82375). Brief link: https://feed.craftedsignal.io/briefs/2026-11-apache-roller-ssrf-cve-2026-82375/
Triage facts
Revision 1- Applicability
- Apache Roller
- Evidence
- Unknown
- Severity
- High
- Sources
- 2 public sources
- Freshness
- Revision 1Nov 16, 18:13 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- A1
Overview
Apache Roller 6.1.5 is vulnerable to Server-Side Request Forgery (SSRF) through legacy outbound Trackback functionality and entry enclosure processing. The Trackback control, while hidden in the standard UI, remains directly reachable. Additionally, the entry enclosure feature allows authors to supply a URL that the server will dereference. No non-default configuration is required to reach internal loopback or private network addresses.
Attack Chain
An authenticated user with entry-editing rights on a weblog can trigger the vulnerable Trackback action or provide a crafted entry enclosure URL. The application default configuration uses an empty allow-list, permitting requests to arbitrary destinations.
Impact
Successful exploitation allows attackers to cause outbound HTTP requests from the server to attacker-chosen destinations. The enclosure handling mechanism further exposes the response status, content type, and length of the requested resources.
Recommendation
Upgrade to Apache Roller 6.1.6 or later. This version removes the outbound trackback action and disables the dereferencing of entry enclosure URLs.
Threat Hunt
Identify web server outbound requests to internal RFC1918 or loopback address ranges originating from the Apache Roller application process, specifically filtering for traffic patterns initiated via Trackback or enclosure handling endpoints.
Data: Network flow logs, Web application server logs, Egress proxy logs