Skip to main content
Menu
CVEs

CVE

Grav privilege escalation in Flex storage keys

Affects Grav 2.0.0 through 2.2.17 where a front-end Flex create form is on a page or a site-built Flex directory accepts entries from accounts. Fixed in 2.2.18.

CVE-2026-130739Published Updated Summary written by a model

8.7HighCNA
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.0.0 through 2.2.17 (Grav 2.x from 2.0.0 up to and including 2.2.17) A front-end Flex create form added to a page, for the create-form overwrite variant A site-built Flex directory the account can create entries in, for the storage key rename variant

Summary

Grav from 2.0.0 before 2.2.18 contains a privilege escalation vulnerability that allows user managers and Flex editors to overwrite, create, or delete accounts by supplying client-controlled storage keys. Attackers can abuse the create form username, cross-type form flash replay, or __META storage key rename to gain super-admin accounts or delete account files.

Who should check

Teams running Grav 2.0.0 through 2.2.17 that have user manager or Flex editor accounts, front-end Flex create forms, or site-built Flex directories

“Grav 2.x from 2.0.0 up to and including 2.2.17”

github.com

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.7/10CVSS 8.7, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Grav 2.0.0 through 2.2.17 (Grav 2.x from 2.0.0 up to and including 2.2.17) A front-end Flex create form added to a page, for the create-form overwrite variant A site-built Flex directory the account can create entries in, for the storage key rename variant
  • 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-130739 (Grav 2.0.0 before 2.2.18 Privilege Escalation via Flex Storage Keys), 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-130739 (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.0.0 through 2.2.17 (Grav 2.x from 2.0.0 up to and including 2.2.17) (source: https://github.com/getgrav/grav/security/advisories/GHSA-6c4v-4wrv-3559)
- A front-end Flex create form added to a page, for the create-form overwrite variant (source: https://github.com/getgrav/grav/security/advisories/GHSA-6c4v-4wrv-3559)
- A site-built Flex directory the account can create entries in, for the storage key rename variant (source: https://github.com/getgrav/grav/security/advisories/GHSA-6c4v-4wrv-3559)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130739 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130739 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-6c4v-4wrv-3559
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-130739
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-130739"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • getgrav grav

    From 2.0.0 · fixed in 2.2.18

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · getgrav/grav · Advisory GHSA-6c4v-4wrv-3559
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130739
RecordNVD · CVE-2026-130739

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130739

Is CVE-2026-130739 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?

Accounts with user-manager or Flex editor rights can overwrite, create or delete accounts, including the super admin's. They can also gain super-admin accounts or destroy account and configuration files.Source: github.com

Which versions are affected by CVE-2026-130739?

grav: from 2.0.0 before 2.2.18.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 is affected. The create-form variant needs a front-end Flex create form added to a page, and the storage key rename variant needs a site-built Flex directory that the account can create entries in. Check your installed Grav version and whether either of these setups exists on your site.Source: github.com

How do I fix CVE-2026-130739?

Upgrade Grav to 2.2.18 or later, which is the fixed version.Source: github.com

More CVEs