Quick answers
- Is CVE-2026-114660 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114660 being exploited in the wild.
- How severe is CVE-2026-114660?
- Medium severity, with a CVSS score of 6.3, published 22 October 2026.
- Which products and versions are affected?
- Grav 2.0.0 before 2.2.5.
- Is there a fix for CVE-2026-114660?
- Yes: fixed in 2.2.5. Until then: Restrict page authoring permissions to trusted users only, and review existing pages for suspicious flex-*@ directives in frontmatter that call methods like setStorageKey() or delete(). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114660 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-114660?
- Check whether you run Grav at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.2.5
Restrict page authoring permissions to trusted users only, and review existing pages for suspicious flex-*@ directives in frontmatter that call methods like setStorageKey() or delete().
Technical details
The FlexDirectory::dynamicFlexField() function processes flex-*@ directives in page frontmatter by calling arbitrary public methods on Flex objects with attacker-controlled arguments, without proper authorization checks. An attacker chains setStorageKey() and delete() method calls to redirect an authorized Flex object to a protected page and delete it. The directives execute only when a user with edit permissions for the named object views the page, running within that user's session and privileges.
Affected products
- Grav Grav 2.0.0 before 2.2.5
Timeline
- 2026-10-07: disclosed
- 2026-10-22: advisory