Skip to content

Grav is vulnerable to Arbitrary File Read

High severity GitHub Reviewed Published Dec 1, 2025 in getgrav/grav • Updated Dec 2, 2025

Package

composer getgrav/grav (Composer)

Affected versions

< 1.8.0-beta.27

Patched versions

1.8.0-beta.27

Description

Summary

  • A low privilege user account with page editing privilege can read any server files using "Frontmatter" form.
  • This includes Grav user account files - /grav/user/accounts/*.yaml. This file stores hashed user password, 2FA secret, and the password reset token.
  • This can allow an adversary to compromise any registered account by resetting a password for a user to get access to the password reset token from the file or by cracking the hashed password.

Details

The vulnerability can be found in /user/plugins/form/templates/forms/fields/display/display.html.twig
image

PoC

  1. This PoC was conducted on Grav CMS version 1.7.46 and Admin Plugin version 1.10.46

image

  1. go to “http://grav.local/admin/pages” then create new page with “Page Template” option set to “Form”.

image

  1. Then go to “Expert” and on Frontmatter input box used to following form template.

image

  1. Save page and go the preview or published page you will see the content of “/etc/passwd” file on the server.

image

Impact

This can allow a low privileged user to perform a full account takeover of other registered users including Administrators. This can also allow an adversary to read any file on the web server. And Due to insufficient permission verification , user who can write a page also can use frontmatter feature using this IDOR vulnerability PoC IDOR mention in CVE-2024-2792

References

@rhukster rhukster published to getgrav/grav Dec 1, 2025
Published by the National Vulnerability Database Dec 1, 2025
Published to the GitHub Advisory Database Dec 2, 2025
Reviewed Dec 2, 2025
Last updated Dec 2, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

EPSS score

Weaknesses

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Learn more on MITRE.

CVE ID

CVE-2025-66300

GHSA ID

GHSA-p4ww-mcp9-j6f2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.