Summary
Grav contains an access-control flaw in the core group blueprint that allows a delegated admin.users operator to assign the admin.super privilege to a group. Affected operators may then gain super-admin capabilities, including access to scheduler and Twig evaluation features, when they can save group configuration.
Affected context
The vulnerability occurs in Grav administration environments where delegated operators can manage user groups and save group definitions through the core group blueprint. It becomes risky when the blueprint does not enforce the required restriction on the access field and the operator can submit a group configuration containing the super-admin permission.
Exploit preconditions
- Attack surface: Grav administrative group-management functionality
- Required access: A delegated administrative account with permission to manage or save user groups
- Trigger point: Processing and saving a group definition containing an elevated
accessvalue - Why exploitation is possible: The group blueprint fails to restrict the sensitive access field to the intended
admin.supersecurity context, allowing a lower-privileged operator to grant super-admin capabilities
Why this happens
The underlying bug is an authorization boundary failure in configuration metadata. A sensitive permission field in the core group blueprint lacks the required security restriction, so a delegated administrator can modify authorization data outside the privilege boundary intended for super-admins. This behavior maps to CWE-269: Improper Privilege Management, because the application permits a principal to acquire or assign privileges beyond those authorized for its role.
Potential impact
- An attacker could gain super-admin access to the Grav administration interface.
- The attacker may modify users, groups, site settings, or other administrative data.
- The attacker could gain scheduler capabilities and influence scheduled application behavior.
- The attacker may access Twig evaluation functionality, potentially increasing the impact of administrative compromise.
- The attacker could alter content or configuration and cause data integrity or availability issues.
General mitigation guidance
Mitigation generally focuses on enforcing authorization at the server-side field and action layers rather than relying on editable blueprint data.
Common defensive patterns include:
- Restricting sensitive group access fields to explicitly authorized super-admin contexts.
- Enforcing server-side allowlists for privileges that delegated administrators may assign.
- Separating user and group administration from changes to privileged security attributes.
- Applying least privilege to administrative roles and limiting scheduler or template-evaluation capabilities.
- Requiring strong review or approval controls for changes affecting authorization policy.
- Treating administrative configuration as protected security-sensitive data and reducing its mutability.
How teams detect issues like this
Detection can include static and behavioral review of authorization configuration:
- Search blueprints and access-control schemas for privileged fields lacking server-side restrictions.
- Review code paths that allow delegated administrators to create or update groups and compare assignable permissions with role definitions.
- Monitor audit logs for changes granting
admin.superor equivalent high-privilege access. - Alert on group modifications performed by delegated operators that introduce administrative permissions.
- Use policy enforcement to require approval for changes to privileged roles and authorization metadata.
- Automated code review and security scanning tools may help identify missing authorization checks, but should be supplemented with permission-boundary testing.

