CVE
Grav information disclosure in user account serialization
Affects Grav 2.x from 2.0.0 up to and including 2.2.17, where the reset token route runs, which needs the Grav 2 API plugin and outgoing mail configured. Fixed in 2.2.18.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.18
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.2.18.
Summary
Grav from 2.0.0 before 2.2.18 contains an information disclosure vulnerability that allows publishers and read-only user managers to read password hashes, 2FA secrets and reset tokens through unfiltered account serialization. Attackers can embed a Flex form for the user-accounts directory in a page or query the Flex API with admin.users.read to obtain super admin credentials and take over the account.
Who should check
Teams running Grav 2.0.0 through 2.2.17 with user accounts, Flex forms, the Grav 2 API plugin or the Login plugin.
Not fixed by: Updating Grav core alone is not enough; Flex Objects must also be updated to 1.4.18.
“Grav 2.x from 2.0.0 up to and including 2.2.17.”
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.2.18.
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-130740 (Grav 2.0.0 before 2.2.18 Information Disclosure of Password Hashes and Reset Tokens), 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-130740 (entry last updated 2026-11-18):
Affected:
- getgrav grav: from 2.0.0, fixed in 2.2.18
Fixed versions: 2.2.18.
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. (source: https://github.com/getgrav/grav/security/advisories/GHSA-4qvf-3fr5-mpq8)
- The reset token route requires the Grav 2 API plugin. (source: https://github.com/getgrav/grav/security/advisories/GHSA-4qvf-3fr5-mpq8)
- The reset token route requires outgoing mail to be configured. (source: https://github.com/getgrav/grav/security/advisories/GHSA-4qvf-3fr5-mpq8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130740 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130740 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-4qvf-3fr5-mpq8
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-130740
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-130740"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- getgrav grav
From 2.0.0 · fixed in 2.2.18
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · getgrav/grav · Advisory GHSA-4qvf-3fr5-mpq8 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130740 |
| Record | NVD · CVE-2026-130740 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130740
Is CVE-2026-130740 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?
A publisher, or an account with only read access to the user directory, can read other accounts' password hashes, 2FA secrets and pending reset tokens. The advisory says this is enough to take over the super admin account.Source: github.com
Which versions are affected by CVE-2026-130740?
grav: from 2.0.0 before 2.2.18.Source: cve.now feed data
Am I affected, and how do I check?
Grav 2.0.0 up to and including 2.2.17 is affected. The reset token route also depends on the Grav 2 API plugin and on outgoing mail being configured, so check the installed Grav version, whether the API plugin is installed, and whether outgoing mail is set up.Source: github.com
How do I fix CVE-2026-130740?
Upgrade Grav to 2.2.18 or later, which is the fixed version.Source: github.com