Origin validation bypass via unanchored Referer prefix
Published Aug 25, 2026 · Updated Aug 28, 2026
Origin validation error in GetGrav Grav before 2.0.16 allows remote attackers to bypass same-origin checks via crafted Referer headers. Uri::referrer() and Pages::referrerRoute() compare the attacker-controlled header with the bare site origin using an unanchored string prefix. Exploitation requires a victim to follow or load a cross-site request from an attacker-controlled lookalike domain; the confirmed consequence is acceptance of an off-site Referer and derivation of an attacker-influenced route.
Summary
What happened
Origin validation error in GetGrav Grav before 2.0.16 allows remote attackers to bypass same-origin checks via crafted Referer headers. Uri::referrer() and Pages::referrerRoute() compare the attacker-controlled header with the bare site origin using an unanchored string prefix. Exploitation requires a victim to follow or load a cross-site request from an attacker-controlled lookalike domain; the confirmed consequence is acceptance of an off-site Referer and derivation of an attacker-influenced route.
The record
- CVE
- CVE-2026-72702
- Published
- Aug 25, 2026
- Updated
- Aug 28, 2026
- Vendor
- GetGrav
- Product
- Grav
- Classifications
- CWE-346
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 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.16
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
- Uri::referrer() unanchored-prefix proof of conceptproof 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