Authenticated SSRF via unrestricted webhook protocols
Published Jul 17, 2026 · Updated Jul 17, 2026
SSRF in Grav before 2.0.4 allows remote authenticated users to read local files or reach internal services through webhooks. WebhookController accepts any URL scheme that FILTER_VALIDATE_URL considers valid, and WebhookDispatcher passes it to curl_init without limiting cURL protocols. Exploitation requires the API plugin and api.webhooks.write permission; triggered deliveries can expose files, process data, or internal-service responses.
Summary
What happened
SSRF in Grav before 2.0.4 allows remote authenticated users to read local files or reach internal services through webhooks. WebhookController accepts any URL scheme that FILTER_VALIDATE_URL considers valid, and WebhookDispatcher passes it to curl_init without limiting cURL protocols. Exploitation requires the API plugin and api.webhooks.write permission; triggered deliveries can expose files, process data, or internal-service responses.
The record
- CVE
- CVE-2026-62234
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- Grav
- Product
- Grav
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 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 <2.0.4
What conditions does exploitation require?
What is affected?
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
- GHSA-58q8-f7v4-w2vf step-by-step reproductionproof of concept · demonstrated
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