CVE-2025-66300: getgrav/grav · Grav is vulnerable to Arbitrary File Read
Affects getgrav/gravSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 8.5 High : upgrade to 1.8.0-beta.27 soon.
Data as of 21 Nov 2026, 03:46 UTC
- Patch
- Available – fixed in 1.8.0-beta.27
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 20 Nov 2026.
What to do
Upgrade getgrav/grav to 1.8.0-beta.27.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistgetgrav/grav | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in Grav CMS version 1.8.0-beta.27 that fixes this vulnerability. Users should upgrade to this version or later to remediate the issue. Since the vulnerability requires page editing privileges, restricting such privileges to trusted users and reviewing user permissions can reduce risk until patched. No other vendor advisory mitigation instructions were provided.
Description
Grav CMS versions prior to 1.8.0-beta.27 contain an Arbitrary File Read vulnerability (CVE-2025-66300) that allows a low privilege user with page editing rights to read any server file via the 'Frontmatter' form. This includes sensitive user account files storing hashed passwords, 2FA secrets, and password reset tokens. Exploiting this flaw can lead to full account takeover of registered users, including administrators, by resetting passwords or cracking hashes. The vulnerability arises from insufficient permission verification in the page editing feature and the frontmatter input handling.