Advisory record · GHSA-m7hx-hw6h-mqmc

Grav File Upload Path Traversal

CVSS 8.8 HighCriticalEPSS 0.61 · 99th percentile

Critical, because:

  • CVSS score 8.8 (7.0 or more) and EPSS 0.61 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 22 Mar 2024, 16:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
getgrav/gravPackagist<1.7.451.7.45
Identifiers
GHSA-m7hx-hw6h-mqmc · CVE-2024-27921 · PKSA-k12q-kcf1-m3gr
Weakness (CWE)
CWE-22
Published
22 Mar 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Grav CMS (Packagist getgrav/grav) versions before 1.7.45 contain a file upload path traversal flaw in the media upload code, where a supplied filename can include directory segments that place uploaded files outside the intended folder. An attacker needs an account with page update permission in the admin area, and the source describes how this could let them replace files such as composer.json or backup archives, which could lead to code execution when Composer commands run or to data exposure. Upgrade to Grav 1.7.45 or later, which is the listed fixed version.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.61, the 99th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:03 UTC First seen by agentprime
  2. 31 Oct 2026, 14:03 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.