Quick answers
- Is CVE-2026-56707 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56707 being exploited in the wild.
- How severe is CVE-2026-56707?
- High severity, with a CVSS score of 7.7, published 25 August 2026.
- Which products and versions are affected?
- Grav Flex Objects 1.4.0 through 1.4.7.
- Is there a fix for CVE-2026-56707?
- A patch was published on 2026-08-10: Flex Objects 1.4.8 released with authorization checks Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56707 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-56707?
- Check whether you run Grav Flex Objects 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.
Technical details
The vulnerability is a missing authorization check (CWE-862) in the FlexObjectsShortcode::renderCollection() method. The shortcode accepts a collection name from a user-controlled attribute and directly calls Flex::getCollection() without verifying the user's permissions against the target directory's authorize ACL. An attacker with page-edit privileges can inject a [flex-objects collection=<type>] shortcode into a published page to render sensitive Flex directories without authorization, bypassing Twig sandbox restrictions. The shortcode was introduced in version 1.4.0 and affected all 1.4.x releases through 1.4.7. A fix was released in version 1.4.8 that adds authorization checks and requires opt-in configuration before a collection can be rendered publicly.
Affected products
- Grav Flex Objects 1.4.0 through 1.4.7
Timeline
- 2026-08-10: disclosed: GitHub security advisory GHSA-x929-528m-vx2m published
- 2026-08-10: patched: Flex Objects 1.4.8 released with authorization checks
- 2026-08-25: advisory: CVE-2026-56707 published