Which versions of Grav CMS are affected by EUVD-2026-42903?

Grav CMS versions before 2.0.2 contain a configuration exfiltration vulnerability that allows authenticated page authors to extract critical credentials including database passwords, API keys, and…. A patch is available.

How to fix or mitigate EUVD-2026-42903?

Within 24 hours: Identify all Grav CMS installations and document versions; audit access logs for template modifications by page author accounts. Within 7 days: Restrict page author permissions to essential users only; rotate all database passwords, API keys, SMTP credentials, and other secrets defined in Grav configuration files. Within 30 days: Monitor vendor advisories for Grav CMS 2.0.2+ release and prepare emergency patching procedures; implement Twig template content inspection controls to detect config access attempts.

Grav CMS EUVD-2026-42903

Q: What is the CVSS score of EUVD-2026-42903?

EUVD-2026-42903 has a CVSS 4.0 base score of 7.1 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

| CVE-2026-61450 HIGH

Code Injection (CWE-94)

2026-07-10 VulnCheck

GHSA-xg8j-6m35-m6wr

PHP RCE Code Injection Grav Getgrav

7.1

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

7.1 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.5 MEDIUM

Network-reachable authoring endpoint (AV:N/AC:L) requires a low-privilege page-author account (PR:L), no interaction, and leaks secrets giving high confidentiality impact with no integrity or availability effect.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 10, 2026 - 16:16 EUVD

Analysis Generated

Jul 10, 2026 - 15:34 vuln.today

DescriptionCVE.org

Grav before 2.0.2 contains a Twig sandbox bypass that allows a page author (any admin.pages user, or anyone able to write to user/pages) to exfiltrate configuration secrets. Although the sandbox replaces the 'config' variable with a redacted facade and strips Config::get/toArray from the method allowlist, the raw container remains accessible via the allow-listed grav.offsetGet('config'), which returns the real Config object. Allow-listed object-dumping filters (json_encode, print_r, yaml_encode) then serialize that object at the PHP level without invoking the sandbox method gate, exposing the full config tree including plugin secrets such as SMTP credentials, API keys, and plugin DB credentials. This is an incomplete fix for GHSA-j274-39qw-32c9.

AnalysisAI

Sensitive configuration exfiltration in Grav CMS before 2.0.2 lets an authenticated page author bypass the Twig sandbox and read the full config tree, including plugin SMTP credentials, API keys, and database passwords. The flaw is an incomplete fix for the earlier GHSA-j274-39qw-32c9 sandbox escape: the redacted 'config' facade is still trivially bypassed through the allow-listed grav.offsetGet('config') call. No public exploit has been identified at time of analysis, though the bypass technique is fully described in the vendor advisory.

Technical ContextAI

Grav is a flat-file PHP CMS that renders page content through Twig templates executed inside a sandbox intended to restrict which objects, methods, and filters page authors can invoke. To harden this boundary, Grav replaces the 'config' Twig variable with a redacted facade and removes Config::get and Config::toArray from the method allowlist. The root cause (CWE-94, code injection) is that the sandbox's method gate is incomplete: the allow-listed grav.offsetGet('config') accessor returns the genuine Config object from the dependency-injection container, and allow-listed serialization filters (json_encode, print_r, yaml_encode) then dump that object at the PHP level, entirely sidestepping the Twig method-invocation gate. The single affected product per CPE is cpe:2.3:a:getgrav:grav (all versions prior to 2.0.2).

RemediationAI

Vendor-released patch: upgrade to Grav 2.0.2 or later, which restores the sandbox method gate against the offsetGet-plus-serialization-filter bypass; see GHSA-mc5q-6hpj-rp7j (https://github.com/getgrav/grav/security/advisories/GHSA-mc5q-6hpj-rp7j). If immediate patching is not possible, restrict the admin.pages permission and filesystem write access to user/pages to fully trusted operators only, since any such user can trigger the leak - the trade-off is reduced delegation of content authoring. As a defense-in-depth step, rotate any secrets that page authors could already have exfiltrated (SMTP credentials, plugin API keys, and plugin/DB passwords) after upgrading, because the patch does not invalidate previously exposed data. Avoid storing high-value credentials in Grav plugin configs where a lower-tier CMS provider can hold them out of band.