CVE-2026-130742: Grav 2.0.0 before 2.2.18 Object Deletion via Flex Sort Field

Published Nov 18, 2026
·
Updated

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.

Affected Software

1 affected component
Grav Grav>=2.0.0<2.2.18

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.2.18

Event History

Nov 18, 2026
CVE Published
via MITRE·11:34 AM
Data Sourced
via MITRE·11:34 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

Any authenticated user with list access to the affected Flex user-accounts API can exploit it. Administrative permissions are not required for the deletion action.

2

What request triggers the destructive behavior?

A GET request to /api/v1/flex-objects/user-accounts with the sort parameter set to delete triggers resolution of delete as a public method. The described request is GET /api/v1/flex-objects/user-accounts?sort=delete.

3

What is the practical impact after account deletion?

The request can delete every account. An attacker can then use the reopened API first-run setup to create a super admin.

4

Are default installations affected?

The provided information identifies affected Grav versions as 2.0.0 before 2.2.18, but does not state whether list access to the user-accounts API is enabled by default.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203