Skip to content
Noroxi
CVE-2025-66302· NVD / CVE Program· CNA GitHub_M

Grav vulnerable to Path Traversal allowing server files backup

Grav is a file-based Web platform. Prior to 1.8.0-beta.27, A path traversal vulnerability has been identified in Grav CMS, allowing authenticated attackers with administrative privileges to read arbitrary files on the underlying server filesystem. This vulnerability arises due to insufficient input sanitization in the backup tool, where user-supplied paths are not properly restricted, enabling access to files outside the intended webroot directory. The impact of this vulnerability depends on the privileges of the user account running the application. This vulnerability is fixed in 1.8.0-beta.27.

MediumCVSS 6.8 · v3.1—No exploit Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Dec 1, 2025
Updated
Sep 25, 2026
EPSS
0.5% · 39th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.8
CNA · GitHub_M
6.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
getgravgrav

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • getgrav gravbefore 1.8.0
  • getgrav grav1.8.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • getgrav grav

    • < 1.8.0-beta.27affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistgetgrav/gravbefore 1.8.0-beta.271.8.0-beta.27

Other highest-scoring records for the same primary product.

  • CVE-2024-27921Grav File Upload Path Traversal vulnerability
    53Plan
  • CVE-2024-34082Grav Arbitrary File Read to Account Takeover
    40Plan
  • CVE-2025-46199Cross Site Scripting vulnerability in grav v.1.7.48 and before allows an attacker to execute arbitrary code via a crafted script to the form
    39Monitor
  • CVE-2026-65008Grav before 2.0.7 Remote Code Execution via Blueprint dynamicData
    38Monitor
  • CVE-2021-47812GravCMS 1.10.7 - Arbitrary YAML Write/Update (Unauthenticated) (2)
    38Monitor
  • CVE-2026-80204Grav before 1.0.18 Authentication Bypass via Scoped API Key
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
getgrav grav1.8.0-beta.27 · descriptionVendor (CNA)
Packagist:getgrav/grav1.8.0-beta.27Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-662950 days apartGrav vulnerable to Path traversal / arbitrary YAML write via user creation leading to Account Takeover / System Corruption
    35Monitor
  • CVE-2026-42608161 days apartGrav: Unauthenticated Path Traversal & Arbitrary File Write in FormFlash component.
    35Monitor
  • CVE-2025-663000 days apartGrav is vulnerable to Arbitrary File Read
    34Monitor
  • CVE-2026-69089245 days apartGrav CMS before 2.0.11 Path Traversal via watermark
    34Monitor
  • CVE-2026-74907260 days apartGrav before 2.0.15 Path Traversal via plugin-asset-map.php
    32Monitor
  • CVE-2026-72697266 days apartGrav CMS before 2.0.16 Path Traversal via media_directory
    28Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records