CVE-2026-100670: Grav CMS 2.0.14 through 2.0.24 Privilege Escalation via Blueprint Guard Bypass
Grav CMS 2.0.14 through 2.0.24 contains a privilege escalation vulnerability in the group and account blueprints. The access map is gated by a security@: admin.super guard that is resolved by the field's exact path, so a submitted flat dot-notation key such as access.admin.super (instead of the nested access[admin][super]) matches no blueprint rule, survives BlueprintSchema::filterArray() and flattening, and is written by FlexObject::update() via setNestedProperty(), which splits on . and reconstructs the nested value. An authenticated backend operator using the flex accounts backend who holds admin.users but not admin.super can therefore grant admin.super to their own account or to a group they belong to and escalate to full super-admin, gaining control over configuration, plugin and theme installation, the file manager, and all accounts. Fixed in 2.0.25, which drops any dotted key whose ancestor path is disabled or marked validate.ignore.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Grav CMSto a version that resolves this vulnerability.Fixed in 2.0.25
Event History
Frequently Asked Questions
Which users can exploit this issue?
An authenticated backend operator using the flex accounts backend is affected if they have the admin.users permission but do not already have admin.super. They can assign admin.super to their own account or to a group they belong to.
What access is required for exploitation?
The attacker needs authenticated access to the backend and access to the flex accounts functionality. Exploitation uses a flat dot-notation field name, such as access.admin.super, rather than the expected nested form submission.
Are fixed versions available?
Yes. Grav CMS 2.0.25 fixes the issue by dropping dotted keys when an ancestor blueprint path is disabled or marked validate.ignore.
How can I identify potentially affected deployments?
Deployments running Grav CMS 2.0.14 through 2.0.24 are in scope. Review backend accounts and group memberships for unexpected admin.super assignments, particularly where users with admin.users permission had access to the flex accounts backend.