Skip to main content
Menu
CVEs

CVE

Grav object deletion via unsafe reflection in Flex sorting

Only affects Grav 2.0.0 through 2.2.17 with a Flex directory sort or filter field that is not a property, such as sort=delete. Fixed in 2.2.18.

CVE-2026-130742Published 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 A Flex directory sort or filter field that is not a property, so it resolves to a public method (for example sort=delete) The full account takeover chain needs the API plugin

Summary

Grav 2.0.0 before 2.2.18 resolves Flex sort and filter field names by first calling them as public methods, so a field named delete invokes FlexObject::delete() without any permission check. Authenticated users with only list access can send GET /api/v1/flex-objects/user-accounts?sort=delete requests to delete every account, then use the reopened API first-run setup to create a super admin.

Who should check

Teams running Grav 2.x from 2.0.0 up to and including 2.2.17, especially with Flex directories such as user accounts or the API plugin enabled

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

github.com

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • 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.7/10CVSS 8.7
  • 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.0.0 through 2.2.17 A Flex directory sort or filter field that is not a property, so it resolves to a public method (for example sort=delete) The full account takeover chain needs the API plugin
  • 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-130742 (Grav 2.0.0 before 2.2.18 Object Deletion via Flex Sort Field), 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-130742 (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 (source: https://github.com/getgrav/grav/security/advisories/GHSA-679v-ch4q-94qm)
- A Flex directory sort or filter field that is not a property, so it resolves to a public method (for example sort=delete) (source: https://github.com/getgrav/grav/security/advisories/GHSA-679v-ch4q-94qm)
- The full account takeover chain needs the API plugin (source: https://github.com/getgrav/grav/security/advisories/GHSA-679v-ch4q-94qm)
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-130742 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130742 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-679v-ch4q-94qm
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-130742
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-130742"}.

Timeline

  1. CVE published
  2. First seen by cve.now

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-679v-ch4q-94qm
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130742
RecordNVD · CVE-2026-130742

Corrections

None so far.

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

Questions about CVE-2026-130742

Is CVE-2026-130742 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 Flex directory sort or filter field that is not a property is called as a public method under its own bare name, so a value such as sort=delete can run that method. An account granted only list access on a Flex directory can then delete data outside that grant.Source: github.com

Which versions are affected by CVE-2026-130742?

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 through 2.2.17 is affected when a Flex directory sort or filter field resolves to a public method. The full account takeover chain also needs the API plugin. To check a site, look at the installed Grav version and whether the API plugin is enabled.Source: github.com

How do I fix CVE-2026-130742?

Upgrade Grav to 2.2.18 or later.Source: github.com

More CVEs