Grav before 1.7.53.7 and 2.x before 2.2.18 contains an authentication bypass vulnerability that allows anonymous
Source GCVE Database
Not known to be exploited · CVSS 9.2 Critical : upgrade to 2.2.18 as a priority.
Data as of 18 Nov 2026, 13:51 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 9.2 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 8.1 |
- Patch
- Available – fixed in 2.2.18, 1.7.53.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
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 17 Nov 2026.
What to do
Upgrade grav to 2.2.18; grav to 1.7.53.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| getgravgrav | Affected
| Fixed in
|
| getgravgrav | Affected
| Fixed in
|
AI-suggested
Upgrade Grav CMS to version 1.7.53.7 or later in the 1.7.x branch, or to version 2.2.18 or later in the 2.x branch, where this vulnerability is fixed. Avoid using Grav installations with paths containing brackets or backslashes as a temporary mitigation if upgrading is not immediately possible.
Description
Grav CMS versions before 1.7.53.7 and 2.x before 2.2.18 have an authentication bypass vulnerability. This flaw allows anonymous users to create or overwrite super-admin accounts due to improper handling of user account counts when the installation path contains brackets or backslashes. The vulnerability arises because UserCollection::count() uses an unescaped glob() pattern, causing the account count to return zero incorrectly. Attackers can exploit this by sending requests to the setup authentication API or the classic admin registration form.