Skip to main content
CVE-2026-130747VulnerabilityPublished

Grav before 1.7.53.7 and 2.x before 2.2.18 contains an authentication bypass vulnerability that allows anonymous

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130747· Critical 9.2

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

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.09.2
CNA (VulnCheck)CVSS 3.18.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
getgravgravAffected
  • >=2.0.0 <2.2.18
Fixed in
  • 2.2.18
getgravgravAffected
  • <1.7.53.7
Fixed in
  • 1.7.53.7

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.

References

Community reviews

Loading reviews…