Grav from 2.0.0 before 2.2.18 contains an information disclosure vulnerability that allows publishers and read-only
Source GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 2.2.18 soon.
Data as of 18 Nov 2026, 13:52 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.5 |
- Patch
- Available – fixed in 2.2.18
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| getgravgrav | 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
A fixed version exists starting from Grav 2.2.18. Users should upgrade to version 2.2.18 or later to remediate this vulnerability. No vendor advisory or patch link is provided in the data, so confirm patch availability from official Grav CMS sources before applying updates.
Description
Grav CMS versions from 2.0.0 up to but not including 2.2.18 contain an information disclosure vulnerability. This flaw allows users with publisher or read-only user manager roles to access sensitive data such as password hashes, two-factor authentication secrets, and reset tokens. The vulnerability arises from unfiltered account serialization, enabling attackers to embed a Flex form for the user-accounts directory in a page or query the Flex API with admin.users.read permissions. Exploiting this can lead to obtaining super admin credentials and full account takeover.