Grav Admin: Missing Username Uniqueness Check · Grav Vulnerable to Privilege Escalation
Affects getgrav/gravSource GCVE Database
Not known to be exploited · CVSS 8.8 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:U/C:H/I:H/A:HExploitation 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
Apply the official fix by upgrading Grav to version 1.8.0-beta.27 or later, where the username uniqueness validation is enforced. Since a patch is available, upgrading is the recommended remediation. No additional mitigations are specified or required beyond applying the update.
Description
A privilege escalation vulnerability in Grav's Admin plugin allows users with create user permission to take over existing administrator accounts by creating a new user with the same username. This flaw enables changing the admin's password and email, granting full administrative control. The issue affects Grav versions prior to 1.8.0-beta.27 and has a high severity rating.