SSRF (Server-Side Request Forgery) in @papra/webhooks (CVE-2026-48051)
Summary
SSRF in @papra/webhooks (CVE-2026-48051). Risk of unauthorized operations or information disclosure. Exploitable via POST /redirect. Mitigation: upgrade to 0.3.3 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48051 has been found in @papra/webhooks.
Attackers can target a specific entry point like POST /redirect over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: upgrade @papra/webhooks to 0.3.3 or later.
If unsure, ask your IT team or search "@papra/webhooks CVE-2026-48051" on the vendor's site.
CVE-2026-48051 (@papra/webhooks) — CWE-918 / CVSS v3 3.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /redirect / POST /api/organizations/{orgId}/webhooks / ofetch / redirect
Patched: 0.3.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in @papra/webhooks. Attackers reach the vulnerable code path via POST /redirect.
Check the vendor advisory for the affected versions of @papra/webhooks. Attack surface: POST /redirect / POST /api/organizations/{orgId}/webhooks / ofetch / redirect.
Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.3.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /redirect requests with malformed payloads or SQL meta-characters. Run grep -r '@papra/webhooks' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@papra/webhooks' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@papra/webhooksを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /redirect' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /redirectへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @papra/webhooks to 0.3.3ステージング環境で 0.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /redirect on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com