Quick answers
- Is CVE-2026-109317 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109317 being exploited in the wild.
- How severe is CVE-2026-109317?
- High severity, with a CVSS score of 7.2, published 12 October 2026.
- Which products and versions are affected?
- Getgrav Grav-Plugin-Api before 1.0.36.
- Is there a fix for CVE-2026-109317?
- Yes: fixed in 1.0.36. Until then: Operators should review existing account and invitation records for scalar admin or api grants and remediate any suspicious entries until an upgrade is available. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109317 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-109317?
- Check whether you run Getgrav Grav-Plugin-Api 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: 1.0.36
Operators should review existing account and invitation records for scalar admin or api grants and remediate any suspicious entries until an upgrade is available.
Technical details
The vulnerability exists in Grav grav-plugin-api versions before 1.0.36, where the permission validation logic fails to properly restrict scalar parent grants during access map updates. While accessGrantsSuper() blocks explicit admin.super and api.super keys, it does not reject positive scalar parent grants that can later be inherited by PermissionResolver::resolve() to satisfy requireSuper() checks. An authenticated attacker with api.users.write permission can exploit this by editing account access maps or invitations to store scalar parent grants, then use those inherited permissions to access super-only API endpoints.
Affected products
- getgrav grav-plugin-api before 1.0.36
Timeline
- 2026-09-23: disclosed
- 2026-10-12: advisory