CVE
Grav authentication bypass in first-run account setup
Only Grav 2.0.0 through 2.2.17 and 1.7 through 1.7.53.6 installs with a bracket pair or a backslash in the absolute install path are exposed. Fixed in 2.2.18 and 1.7.53.7.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.18, 1.7.53.7
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Grav 2.x from 2.0.0 up to and including 2.2.17, or Grav 1.7 up to and including 1.7.53.6. Install path contains a bracket pair [...] or a backslash somewhere in the absolute path.
Summary
Grav before 1.7.53.7 and 2.x before 2.2.18 contains an authentication bypass vulnerability that allows anonymous visitors to create super-admin accounts because UserCollection::count() uses an unescaped glob() pattern. On installs whose path contains brackets or a backslash, the account count returns zero, so attackers can send requests to POST /api/v1/auth/setup or the classic admin registration form to create or overwrite administrator accounts.
Who should check
Teams running Grav 2.x or 1.7 installs whose filesystem path contains square brackets or a backslash, including Grav sites using the classic admin plugin.
Not fixed by: Update the API plugin to 1.1.6 as well on Grav 2 sites.
“Grav 2.x from 2.0.0 up to and including 2.2.17, and Grav 1.7 up to and including 1.7.53.6”
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.2, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Grav 2.x from 2.0.0 up to and including 2.2.17, or Grav 1.7 up to and including 1.7.53.6. Install path contains a bracket pair [...] or a backslash somewhere in the absolute path.Upgrade to a fixed version: 2.2.18, 1.7.53.7.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130747 (Grav before 1.7.53.7 and 2.x before 2.2.18 Authentication Bypass via First-Run Setup), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130747 (entry last updated 2026-11-18):
Affected:
- getgrav grav: from 2.0.0, fixed in 2.2.18
- getgrav grav: fixed in 1.7.53.7
Fixed versions: 2.2.18, 1.7.53.7.
Conditions (all must be true for the bug to be hit):
- Grav 2.x from 2.0.0 up to and including 2.2.17, or Grav 1.7 up to and including 1.7.53.6. (source: https://github.com/getgrav/grav/security/advisories/GHSA-gjx7-95hg-x969)
- Install path contains a bracket pair [...] or a backslash somewhere in the absolute path. (source: https://github.com/getgrav/grav/security/advisories/GHSA-gjx7-95hg-x969)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130747 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130747 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/getgrav/grav/security/advisories/GHSA-gjx7-95hg-x969
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130747
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130747"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- getgrav grav
From 2.0.0 · fixed in 2.2.18
- getgrav grav
fixed in 1.7.53.7
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · getgrav/grav · Advisory GHSA-gjx7-95hg-x969 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130747 |
| Record | NVD · CVE-2026-130747 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130747
Is CVE-2026-130747 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The first-run setup flaw lets an anonymous visitor create a super-admin account, or overwrite the existing administrator account under a password the visitor chooses.Source: github.com
Which versions are affected by CVE-2026-130747?
grav: from 2.0.0 before 2.2.18. grav: before 1.7.53.7.Source: cve.now feed data
Am I affected, and how do I check?
Grav 2.x from 2.0.0 up to and including 2.2.17, and Grav 1.7 up to and including 1.7.53.6. Only installs whose absolute install path contains a [...] bracket pair or a backslash are exposed, so check the version and the install path.Source: github.com
How do I fix CVE-2026-130747?
Upgrade Grav 2.x to 2.2.18 or later, or Grav 1.7 to 1.7.53.7 or later.Source: github.com