CVE-2026-92917: Exposure of Sensitive Information to an Unauthorized Actor in getgrav grav
A vulnerability in Grav CMS versions 2.0.0-rc.1 through 2.0.21 allows authenticated users with page-edit rights to expose sensitive configuration information. This occurs because the Twig content sandbox does not properly restrict certain filters, enabling dumping of the entire merged configuration including secrets like SMTP credentials and API tokens. The issue is fixed in version 2.0.22.
AI Analysis
Technical Summary
Grav CMS versions 2.0.0-rc.1 through 2.0.21 contain a vulnerability in the Twig content sandbox implementation. The sandbox fails to restrict the dump and serialize filters (print_r, vardump, json_encode, yaml_encode, string) because GravExtension::assertSandboxDumpSafe() calls SandboxExtension::isSandboxed() without a Source argument, which only checks a global sandbox flag that Grav never enables. Consequently, an authenticated user with page-edit permissions can render Twig content such as {{ config|print_r }} to dump the entire merged configuration, bypassing path redaction and exposing sensitive plugin secrets including SMTP credentials, API tokens, webhook secrets, and cache backend passwords. Grav 1.7 is not affected as it does not include a Twig content sandbox. The vulnerability is addressed in Grav 2.0.22 by registering the affected filters with Twig's needs_is_sandboxed flag.
Potential Impact
An authenticated user with page-edit rights can access and disclose sensitive configuration data including credentials and secrets. This exposure can lead to further compromise of the system or connected services. The vulnerability does not require privilege escalation beyond page-edit rights but allows unauthorized disclosure of sensitive information.
Mitigation Recommendations
Upgrade Grav CMS to version 2.0.22 or later, where the vulnerability is fixed by properly restricting the affected Twig filters. No other mitigations are indicated by the vendor advisory.
CVE-2026-92917: Exposure of Sensitive Information to an Unauthorized Actor in getgrav grav
Description
A vulnerability in Grav CMS versions 2.0.0-rc.1 through 2.0.21 allows authenticated users with page-edit rights to expose sensitive configuration information. This occurs because the Twig content sandbox does not properly restrict certain filters, enabling dumping of the entire merged configuration including secrets like SMTP credentials and API tokens. The issue is fixed in version 2.0.22.
CVSS v4.0
Score 8.7high
Affected software
getgrav
grav
pkg:github/getgrav/gravRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Grav CMS versions 2.0.0-rc.1 through 2.0.21 contain a vulnerability in the Twig content sandbox implementation. The sandbox fails to restrict the dump and serialize filters (print_r, vardump, json_encode, yaml_encode, string) because GravExtension::assertSandboxDumpSafe() calls SandboxExtension::isSandboxed() without a Source argument, which only checks a global sandbox flag that Grav never enables. Consequently, an authenticated user with page-edit permissions can render Twig content such as {{ config|print_r }} to dump the entire merged configuration, bypassing path redaction and exposing sensitive plugin secrets including SMTP credentials, API tokens, webhook secrets, and cache backend passwords. Grav 1.7 is not affected as it does not include a Twig content sandbox. The vulnerability is addressed in Grav 2.0.22 by registering the affected filters with Twig's needs_is_sandboxed flag.
Potential Impact
An authenticated user with page-edit rights can access and disclose sensitive configuration data including credentials and secrets. This exposure can lead to further compromise of the system or connected services. The vulnerability does not require privilege escalation beyond page-edit rights but allows unauthorized disclosure of sensitive information.
Mitigation Recommendations
Upgrade Grav CMS to version 2.0.22 or later, where the vulnerability is fixed by properly restricting the affected Twig filters. No other mitigations are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-17T11:07:29.772Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aabcfb855bf5e2cf54dbe54
Added to database: 09/17/2026, 11:32:08 UTC
Last enriched: 09/17/2026, 11:46:29 UTC
Last updated: 09/17/2026, 12:38:59 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.