CVE-2026-130742

Grav 2.0.0 before 2.2.18 Object Deletion via Flex Sort Field

Published Nov 18, 2026 CVSS 4.0 · 8.7 High EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Grav 2.0.0 through 2.2.18 resolves Flex sort and filter field names by first calling them as public methods, enabling a field named delete to invoke FlexObject::delete() without any permission check. This flaw allows a user with only list‑level credentials to delete all accounts by sending a GET request to the flex‑objects API with a sort parameter of delete, and then create a super administrator through the API first‑run setup. The result is total loss of user accounts and the ability to gain full administrative control of the site.

Affected Systems

The vulnerability affects the Grav content‑management system by Getgrav, specifically versions 2.0.0 up to and including 2.2.18. No other versions are listed as impacted by the CNA.

Risk and Exploitability

The CVSS score of 8.7 reflects high severity, and the EPSS score is not available, meaning there is no current exploitation probability data, but the KEV catalog does not list this CVE. An attacker with authentication that allows list access can exploit the issue through a crafted API request; no additional system exposure or out‑of‑band attack is required. The vulnerability can be leveraged to eliminate all user accounts and subsequently create a super administrator, effectively giving the attacker full control over the web application.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the Grav 2.2.18 update or later to patch the delete field issue.
  • Restrict Flex Object API access to trusted users by enforcing stricter authentication and permission checks beyond list‑level access.
  • Audit the API logs for unexpected delete calls and configure monitoring or alerting on such activity to detect misuse early.

Generated by OpenCVE AI on November 18, 2026 at 19:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description 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.
Title Grav 2.0.0 before 2.2.18 Object Deletion via Flex Sort Field
First Time appeared Getgrav
Getgrav grav
Weaknesses CWE-470
CPEs cpe:2.3:a:getgrav:grav:*:*:*:*:*:*:*:*
Vendors & Products Getgrav
Getgrav grav
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-470

    Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 18, 2026, 11:34 AM
Reserved
Nov 17, 2026, 3:40 PM
Status
Deferred
Published
Nov 18, 2026, 12:17 PM
Modified
Nov 18, 2026, 12:17 PM