Grav CMS before 2.0.16 contains an origin validation bypass in the Uri::referrer() and Pages::referrerRoute() methods, which validate the Referer header using an unanchored string prefix match (str_starts_with($referrer, $base)) with no trailing delimiter. An attacker who controls a domain that begins with the victim site's origin (e.g. https://example.com.attacker.tld) can send a request with such a Referer to be treated as same-origin, bypassing the Referer-based origin check.
CVE-2026-72702
Score 5.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026Grav CMS before 2.0.16 Origin Validation Bypass via Referer | Advisories | VulnCheck
https://www.vulncheck.com/advisories/grav-cms-before-origin-validation-bypass-via-refererOrigin validation bypass in Uri::referrer() and Pages::referrerRoute() via unanchored prefix match · Advisory · getgrav/grav · GitHub
https://github.com/getgrav/grav/security/advisories/GHSA-9ccq-2jfg-qw33Vendor Advisories for CVE-2026-72702(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 04:13 UTCEG score recompute
- 2026-08-26 04:13 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 02:19 UTCEG score recompute
- 2026-08-25 01:50 UTCEG score recompute
- 2026-08-25 01:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-346
Frequently asked(5)
What is CVE-2026-72702?
When was CVE-2026-72702 disclosed?
Is CVE-2026-72702 actively exploited?
What is the CVSS score of CVE-2026-72702?
How do I remediate CVE-2026-72702?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72702
Is Your Infrastructure Affected by CVE-2026-72702?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.