CVE-2026-130742
8.8HighPublished 18 Nov 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-470
What an attacker gets
Authenticated attackers can delete all user accounts and create a new super admin. They only need standard list access to the Grav API to trigger this.
Root cause
The application incorrectly resolves Flex sort and filter field names by invoking them as public methods without permission checks.
Affected versions
Grav 2.0.0 through 2.2.17
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade to Grav 2.2.18 or later. If you cannot patch immediately, restrict access to the /api/v1/flex-objects/ endpoint via your web server configuration.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.