{"items":[{"id":"NVI-00004639","kind":"vulnerability","title":"Grav: Origin validation bypass in Uri::referrer() and Pages::referrerRoute() via unanchored prefix match","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-9ccq-2jfg-qw33","CVE-2026-72702"],"plain_summary":"OSV carries this publisher advisory for getgrav/grav. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.0.16 for getgrav/grav. Confirm the publisher’s latest guidance.","source_ids":["sr-6df01121c24b5a45e1134c737fd91a66"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-13e8497a821c6d244e880971f6e0b193"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-12T15:10:00.207Z","value":"5.4 MEDIUM (3.1)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-13e8497a821c6d244e880971f6e0b193"},{"kind":"CVSS","as_of":"2026-10-12T15:10:00.207Z","value":"9.3 CRITICAL (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-13e8497a821c6d244e880971f6e0b193"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-6df01121c24b5a45e1134c737fd91a66","url":"https://github.com/advisories/GHSA-9ccq-2jfg-qw33","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9ccq-2jfg-qw33","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.684Z"},{"id":"sr-13e8497a821c6d244e880971f6e0b193","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72702","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-72702","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:49.802Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6df01121c24b5a45e1134c737fd91a66"],"technology":"getgrav/grav","known_exclusions":[],"conditions_summary":"## Summary\n\n`Grav\\Common\\Uri::referrer()` and `Grav\\Common\\Page\\Pages::referrerRoute()` both check whether an incoming request's `Referer` header \"came from our site\" using `str_starts_with($referrer, $base)`, where `$base` is the site's own absolute root URL (for example `https://example.com`, no trailing slash). Because the comparison has no boundary character after the prefix, any `Referer` value that merely starts with that string is accepted, including a `Referer` from a completely different host such as `https://example.com.attacker.tld`.\n\nThis is the same class of bug already fixed once in 2.0.15 for the fast static asset server (GHSA-4v9q-p283-qc2m, \"also allowing any neighbouring directory whose name starts with the same letters\"). The identical pattern is still present in both places that trust the `Referer` header, and neither is covered by that fix.\n\n## Affected product and version\n\nProduct: Grav CMS, getgrav/grav\nConfirmed present in: 2.0.15, commit c2b46866857a93a0aa7048e7ed707ed3ed45dbc3\nThe pattern is not touched by any of the 2.0.15 security fixes, so earlier 2.x releases are likely affected too. I have not checked how far back it goes.\n\n## Affected code\n\n`system/s","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.0.16"]}],"null_published_at":"2026-11-01T14:34:07.530Z","source_updated_at":"2026-09-17T20:45:05.209Z","source_disclosed_at":"2026-09-17T20:24:38.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:10.684Z"},{"id":"NVI-00004639","kind":"vulnerability","title":"Grav: Origin validation bypass in Uri::referrer() and Pages::referrerRoute() via unanchored prefix match","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-9ccq-2jfg-qw33","CVE-2026-72702"],"plain_summary":"OSV carries this publisher advisory for getgrav/grav. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.0.16 for getgrav/grav. Confirm the publisher’s latest guidance.","source_ids":["sr-6df01121c24b5a45e1134c737fd91a66"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-6df01121c24b5a45e1134c737fd91a66","url":"https://github.com/advisories/GHSA-9ccq-2jfg-qw33","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9ccq-2jfg-qw33","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.684Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6df01121c24b5a45e1134c737fd91a66"],"technology":"getgrav/grav","known_exclusions":[],"conditions_summary":"## Summary\n\n`Grav\\Common\\Uri::referrer()` and `Grav\\Common\\Page\\Pages::referrerRoute()` both check whether an incoming request's `Referer` header \"came from our site\" using `str_starts_with($referrer, $base)`, where `$base` is the site's own absolute root URL (for example `https://example.com`, no trailing slash). Because the comparison has no boundary character after the prefix, any `Referer` value that merely starts with that string is accepted, including a `Referer` from a completely different host such as `https://example.com.attacker.tld`.\n\nThis is the same class of bug already fixed once in 2.0.15 for the fast static asset server (GHSA-4v9q-p283-qc2m, \"also allowing any neighbouring directory whose name starts with the same letters\"). The identical pattern is still present in both places that trust the `Referer` header, and neither is covered by that fix.\n\n## Affected product and version\n\nProduct: Grav CMS, getgrav/grav\nConfirmed present in: 2.0.15, commit c2b46866857a93a0aa7048e7ed707ed3ed45dbc3\nThe pattern is not touched by any of the 2.0.15 security fixes, so earlier 2.x releases are likely affected too. I have not checked how far back it goes.\n\n## Affected code\n\n`system/s","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.0.16"]}],"null_published_at":"2026-10-31T22:12:57.136Z","source_updated_at":"2026-09-17T20:45:05.209Z","source_disclosed_at":"2026-09-17T20:24:38.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:10.684Z"}],"next_cursor":null,"snapshot_revision":"42594"}