Account metadata disclosure via unauthorized title rendering
Published Dec 1, 2025 · Updated Dec 2, 2025
IDOR in the Grav Admin Panel before 1.8.0-beta.27 allows remote authenticated users to read other accounts' email addresses. The account edit view resolves a username from /admin/accounts/users/{username} and renders that account's email in the title before authorization denial. A zero-privilege account is sufficient; the request returns HTTP 403, but the response source still discloses email and other account metadata.
Summary
What happened
IDOR in the Grav Admin Panel before 1.8.0-beta.27 allows remote authenticated users to read other accounts' email addresses. The account edit view resolves a username from /admin/accounts/users/{username} and renders that account's email in the title before authorization denial. A zero-privilege account is sufficient; the request returns HTTP 403, but the response source still discloses email and other account metadata.
The record
- CVE
- CVE-2025-66306
- Published
- Dec 1, 2025
- Updated
- Dec 2, 2025
- Vendor
- GetGrav
- Product
- Grav
- Classifications
- CWE-639, T1087
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 1, 2025CVE publishedPublication date reported by the CVE source.
- Dec 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.8.0-beta.27
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Authenticated account-endpoint reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo