CVE-2025-66301: getgrav grav · Improper Authorization
Affects getgrav gravSource CVE Database V5
Public exploit available (Metasploit) · CVSS 8.6 High · fixed in 1.8.0 : patch getgrav grav as a priority.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.3% chance of exploitation in 30 days – higher than 71% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubgetgrav/gravpkg:github/getgrav/gravOther threats | 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
The primary mitigation is to upgrade all Grav installations to version 1.8.0-beta.27 or later, where the authorization checks have been corrected. Until upgrades can be applied, organizations should restrict editor permissions to prevent access to the YAML frontmatter fields, especially the data[_json][header][form] section. Implement strict role-based access controls (RBAC) to limit who can modify form processing configurations. Additionally, monitor and audit changes to page configurations and form processing logic for unauthorized modifications. Employ web application firewalls (WAFs) to detect and block suspicious POST requests targeting /admin/pages/{page_name}. Regularly review and harden CMS configurations and ensure that editors are trained on security best practices. Finally, maintain an incident response plan to quickly address any detected exploitation attempts.
Description
Grav is a file-based Web platform. Prior to 1.8.0-beta.27, due to improper authorization checks when modifying critical fields on a POST request to /admin/pages/{page_name}, an editor with only permissions to change basic content on the form is now able to change the functioning of the form through modifying the content of the data[_json][header][form] which is the YAML frontmatter which includes the process section which dictates what happens after a user submits the form which include some important actions that could lead to further vulnerabilities. This vulnerability is fixed in 1.8.0-beta.27.