/

CVE-2026-56707

Severity:

HIGH RISK

(7.7)

Authorization Bypass (CWE-862) in Grav Flex Objects

CVE-2026-56707

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-862

Impact:

Unauthorized Information Disclosure

Severity:

HIGH RISK

(7.7)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Grav Flex Objects versions 1.4.0 through 1.4.7 contain an authorization bypass in the flex-objects shortcode. A user with page-edit access may place the shortcode in a published page to render registered Flex collections without the permission checks normally enforced by the admin panel, potentially exposing sensitive directory contents such as user account information.

Affected context

The vulnerability occurs in Grav deployments using the Flex Objects plugin and the flex-objects shortcode. It becomes risky when a user who can edit page content can publish or influence a page containing the shortcode, while collection authorization is enforced only through administrative controls rather than during shortcode rendering.

Exploit preconditions

  • Attack surface: Published Grav page content processed by the flex-objects shortcode
  • Required access: Page-edit access sufficient to insert or modify shortcode content
  • Trigger point: A visitor loads a page containing the attacker-controlled shortcode
  • Why exploitation is possible: Shortcode rendering can access registered Flex collections without applying the corresponding administrative authorization checks

Why this happens

The underlying bug is an authorization enforcement gap. The shortcode handler permits access to registered Flex collections based on page content processing but does not consistently evaluate the permissions that protect those collections in the admin panel. This maps to CWE-862: Missing Authorization, where an operation is available without verifying whether the requesting user is allowed to perform it.

Potential impact

  • Sensitive directory contents may be disclosed to page visitors
  • User account information could be exposed
  • Collection data may be rendered outside its intended audience
  • Attackers could use exposed information to support follow-on attacks

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the point where Flex collections are selected and rendered, rather than relying solely on administrative interface controls.

Common defensive patterns include:

  • Applying collection-level permission checks to every shortcode rendering path
  • Using secure-by-default behavior that denies access unless explicitly authorized
  • Restricting which collections may be referenced from user-editable page content
  • Reducing trust in content authors by separating content-editing rights from data-access rights
  • Limiting exposure of account and directory data through field-level filtering
  • Running content and application processes with only the privileges required for their roles

How teams detect issues like this

Organizations can identify similar authorization gaps through:

  • Static analysis of shortcode handlers for missing permission checks before data retrieval
  • Code review signals where administrative ACLs are enforced in one interface but not in alternate rendering paths
  • Tests that compare authorization behavior between admin, API, shortcode, and published-page contexts
  • Policy enforcement requiring explicit authorization checks before collection queries or record rendering
  • Monitoring published content for newly introduced data-rendering shortcodes and unusual access to protected collections

Automated code review and security testing tools may help identify inconsistent access-control enforcement.

Sources

SourceLink
github.comgithub.com/getgrav/grav/security/advisories/GHSA-x929-528m-vx2m
vulncheck.comvulncheck.com/advisories/grav-flex-objects-through-authorization-bypass-via-shortcode

Frequently asked

questions

An attacker generally needs page-edit access or another capability that allows them to insert the flex-objects shortcode into content that visitors can load.

Not necessarily. The issue is that page-edit access may be sufficient to bypass collection permissions that would otherwise be enforced in the administrative interface.

Enforce authorization checks whenever a Flex collection is selected or rendered, including through shortcodes and other alternate content-processing paths.

Test every data-access interface under multiple user roles, apply deny-by-default collection permissions, and ensure that content-editing privileges do not implicitly grant access to protected data.

Find out what's already
exploitable in your codebase.