Papra: SSRF via HTTP redirect bypass in webhook delivery
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| papra-hq | papra | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Papra-hq | Papra |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5g86-85rp-f9hx | Papra HTTP redirect bypass can lead to SSRF via webhook delivery system |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.255% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Papra-hq
Papra-hq papra |
|
| Vendors & Products |
Papra-hq
Papra-hq papra |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Papra is a minimalistic document management and archiving platform. Prior to version 26.5.0, Papra's webhook delivery system contains an SSRF protection bypass that allows any authenticated organisation member to cause the server to make HTTP requests to internal addresses — loopback, link-local, and RFC-1918 ranges. The SSRF protection validates the registered webhook URL but ignores redirect destinations. The HTTP client (ofetch) follows 3xx responses automatically, and the redirect target is never checked against the blocklist. An attacker registers a webhook pointing to an attacker-controlled server, which redirects incoming POSTs to any internal address. Exploitation was confirmed by live test against the official Docker image. The fix is a single-line change to the webhook HTTP client. This issue has been patched in version 26.5.0. | |
| Title | Papra: SSRF via HTTP redirect bypass in webhook delivery | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|