Skip to main content
VulnerabilityPublished

CVE-2026-72820: getgrav grav · Path Traversal

Affects getgrav gravSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2.0.13 when convenient.

Data as of 13 Nov 2026, 23:54 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.13
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 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 13 Nov 2026.

What to do

Upgrade getgrav grav to 2.0.13.

Affected software

ProductAffectedFixed in
getgravgravAffected
  • >=2.0.11 <2.0.13
Fixed in
  • 2.0.13
GitHubgetgrav/gravpkg:github/getgrav/gravOther threatsAffected
  • =2.0.11
Fixed in–

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

AI-suggested

If you cannot patch yet, restrict profile editor access to trusted users only and monitor backup profile configurations for suspicious path traversal attempts.

Description

Grav versions before 2.0.13 contain a path traversal vulnerability in the backup profile root path validation. This flaw allows attackers with profile editor access to configure backup profiles that archive directories outside the intended GRAV_ROOT directory, potentially exposing sensitive files from system locations such as /opt, /mnt, or /srv. The vulnerability arises because the validation does not properly restrict paths not included in a hard-coded deny-list.

References

Community reviews

Loading reviews…