Authenticated blind SSRF via webhook URL validation
Published Aug 5, 2026 · Updated Aug 5, 2026
SSRF in Firefly III allows remote authenticated users to send blind webhook requests to loopback or internal services. IsValidWebhookUrl explicitly accepts 127.0.0.0/8 and validates one gethostbyname result, while StandardWebhookSender lets Guzzle resolve the host again. Webhooks must be enabled, which is not the default, and response bodies remain in server-side debug logs rather than being returned to the user.
Summary
What happened
SSRF in Firefly III allows remote authenticated users to send blind webhook requests to loopback or internal services. IsValidWebhookUrl explicitly accepts 127.0.0.0/8 and validates one gethostbyname result, while StandardWebhookSender lets Guzzle resolve the host again. Webhooks must be enabled, which is not the default, and response bodies remain in server-side debug logs rather than being returned to the user.
The record
- CVE
- CVE-2026-71250
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- Firefly III
- Product
- Firefly III
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=0
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.
Weakness, pattern, technique
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo