CVE
Grav privilege escalation to super admin via user groups
Affects Grav 2.0.0 through 2.2.17 where a user manager holds admin.users.update and front-end Flex edit forms for user-groups and user-accounts exist. Fixed in 2.2.18.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.18
- 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 A super admin has delegated user management to the attacker, who holds admin.users.update Front-end pages with the Flex edit forms for user-groups and user-accounts exist on the site The victim's super access comes from a group instead of the account's own access map
Summary
Grav from 2.0.0 before 2.2.18 contains a privilege escalation vulnerability that allows user managers with admin.users.update to take over super admin accounts by disabling the super-granting group. Attackers can set the group's enabled field to false via the Flex user-groups form, then reset the victim's password through the user-accounts form to gain super admin access.
Who should check
Teams running Grav 2.x CMS from 2.0.0 through 2.2.17 that delegate user management to non-super admin accounts and use front-end Flex user-groups and user-accounts forms
“Grav 2.x from 2.0.0 up to and including 2.2.17”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
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 A super admin has delegated user management to the attacker, who holds admin.users.update Front-end pages with the Flex edit forms for user-groups and user-accounts exist on the site The victim's super access comes from a group instead of the account's own access mapUpgrade 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-130738 (Grav 2.0.0 before 2.2.18 Privilege Escalation via User Group Enabled Toggle), 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-130738 (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-mh59-vjm5-j5rc)
- A super admin has delegated user management to the attacker, who holds admin.users.update (source: https://github.com/getgrav/grav/security/advisories/GHSA-mh59-vjm5-j5rc)
- Front-end pages with the Flex edit forms for user-groups and user-accounts exist on the site (source: https://github.com/getgrav/grav/security/advisories/GHSA-mh59-vjm5-j5rc)
- The victim's super access comes from a group instead of the account's own access map (source: https://github.com/getgrav/grav/security/advisories/GHSA-mh59-vjm5-j5rc)
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, high-privilege login, no user action.
CISA KEV: CVE-2026-130738 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130738 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-mh59-vjm5-j5rc
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-130738
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-130738"}.Timeline
- CVE published
- First seen by cve.now
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-mh59-vjm5-j5rc |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130738 |
| Record | NVD · CVE-2026-130738 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130738
Is CVE-2026-130738 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 user manager, given user-management rights by a super admin, can make themselves a super admin, which gives full control of the site.Source: github.com
Which versions are affected by CVE-2026-130738?
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 setup also needs a super admin who has delegated user management to a manager holding admin.users.update, front-end pages with Flex edit forms for user-groups and user-accounts, and a victim whose super access comes from a group rather than the account's own access map. Check the installed Grav version and whether those front-end Flex edit pages exist on the site.Source: github.com
How do I fix CVE-2026-130738?
Upgrade Grav to 2.2.18 or later, the first fixed version.Source: github.com