Skip to main content
CVE-2026-130745VulnerabilityPublished

Grav from 2.0.0 before 2.2.18 contains an access control bypass vulnerability that allows anonymous visitors to read

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130745· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 2.2.18 soon.

Data as of 18 Nov 2026, 13:52 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.2
CNA (VulnCheck)CVSS 3.15.9
Patch
Available – fixed in 2.2.18
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade grav and getgrav/grav to 2.2.18.

Affected software

ProductAffectedFixed in
getgravgravAffected
  • >=2.0.0 <2.2.18
Fixed in
  • 2.2.18
GitHubgetgrav/gravpkg:github/getgrav/gravOther threatsAffected
  • >=2.0.0 <2.2.18
Fixed in
  • 2.2.18

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Grav CMS version 2.2.18. Users should upgrade to version 2.2.18 or later to resolve this access control bypass vulnerability. No additional mitigation steps are indicated.

Description

Grav CMS versions from 2.0.0 up to but not including 2.2.18 have an access control bypass vulnerability. This flaw allows anonymous visitors to read protected pages because the admin and site scopes share a page cache key. The issue arises when routine editor activity via the API plugin rebuilds the page index without enforcing frontmatter.yaml access rules, temporarily exposing members-only content until the cache is refreshed.

References

Community reviews

Loading reviews…