CVE-2026-72698
Received Received - Intake

Grav CMS Configuration Array Exposure via Twig Sandbox

Vulnerability report for CVE-2026-72698, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-25

Last updated on: 2026-08-25

Assigner: VulnCheck

Description

Grav CMS before 2.0.16 fails to filter system, site, and theme configuration arrays in sandboxed Twig renders, allowing content editors to read sensitive configuration values. Attackers with page-content edit access can access raw configuration arrays including secrets like cache credentials by using dot notation in Twig templates, bypassing the config_denied_paths restrictions.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-25
Last Modified
2026-08-25
Generated
2026-08-25
AI Q&A
2026-08-25
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
grav cms to 2.0.16 (exc)
getgrav grav to 2.0.16 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Grav CMS before version 2.0.16 has a flaw where system, site, and theme configuration arrays are not properly filtered in sandboxed Twig renders. This allows content editors with page-content edit access to read sensitive configuration values, including secrets like cache credentials, by using dot notation in Twig templates. The vulnerability bypasses the config_denied_paths restrictions because the sandbox security policy cannot restrict array key access, only object method and property access.

Detection Guidance

Check Grav CMS version with: grep -r "version" /path/to/grav/vendor/composer/installed.json. If version is below 2.0.16, the system is vulnerable. Inspect Twig templates for suspicious dot notation usage like {{ system.cache.redis.password }} in page content.

Review logs for unauthorized access attempts to configuration paths. Monitor for unusual template rendering errors that may indicate sandbox bypass attempts.

Impact Analysis

If you are a Grav CMS user with page-content edit access, an attacker could exploit this to read sensitive configuration data, including credentials for caches or other services. This could lead to unauthorized access to system resources, data breaches, or further compromise of the CMS environment.

Compliance Impact

This vulnerability could lead to unauthorized exposure of sensitive data, such as credentials or configuration details, which may violate compliance requirements under GDPR (data protection) or HIPAA (health information privacy). Unauthorized access to such data could result in regulatory penalties or legal consequences.

Mitigation Strategies

Upgrade Grav CMS to version 2.0.16 or later immediately. Apply the patch from the official Grav CMS repository or use the provided security advisory fixes.

Restrict page-content edit access to trusted users only. Review and remove any existing Twig templates using dot notation to access system, site, or theme variables.

Rotate all exposed credentials including cache passwords and API keys. Monitor system logs for any signs of exploitation attempts after mitigation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72698. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart