File read and internal access via webhook SSRF
Published Aug 19, 2026 · Updated Aug 19, 2026
Server-side request forgery in Grav API Plugin before 1.0.6 allows remote authenticated users to read local or internal data via webhook URLs. WebhookController.php accepts attacker-supplied targets after only FILTER_VALIDATE_URL syntax checks, and WebhookDispatcher.php starts cURL without CURLOPT_PROTOCOLS or CURLOPT_REDIR_PROTOCOLS restrictions, so file, dict, gopher, private-network, and link-local destinations can be reached and their response bodies recovered from webhook deliveries. Reachability requires an account with the api.webhooks.write permission, and the exposed data is limited to what the Grav host itself can fetch, including local files, internal services, and cloud metadata endpoints.
Summary
What happened
Server-side request forgery in Grav API Plugin before 1.0.6 allows remote authenticated users to read local or internal data via webhook URLs. WebhookController.php accepts attacker-supplied targets after only FILTER_VALIDATE_URL syntax checks, and WebhookDispatcher.php starts cURL without CURLOPT_PROTOCOLS or CURLOPT_REDIR_PROTOCOLS restrictions, so file, dict, gopher, private-network, and link-local destinations can be reached and their response bodies recovered from webhook deliveries. Reachability requires an account with the api.webhooks.write permission, and the exposed data is limited to what the Grav host itself can fetch, including local files, internal services, and cloud metadata endpoints.
The record
- CVE
- CVE-2026-62668
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- Grav
- Product
- Grav
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=< 2.0.4
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