Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged page editor
-
ExploitAuthor Twig page rendering Clockwork token
-
ExecutionReplay token in X-Clockwork-Auth header
-
ImpactRead profiler config, metadata, and DB queries
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated Grav account with page-editor privileges and the ability to author Twig in pages, on versions 2.0.22 up to (but not including) 2.1.7; the Clockwork debugger must be active so that profiler records and a system.debugger.token value exist. Exploitation is limited by the need for valid editor credentials and Twig-authoring rights - it is not anonymously reachable - and is remediated by upgrading to 2.1.7, which adds system.debugger.token to the sandbox redaction list. |
| Impact | This is a moderate-priority information disclosure flaw, not a critical emergency. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) and the 7.1 score agree that exploitation is network-reachable, low-complexity, requires no user interaction, but does require privileges (PR:L) - i.e. an already-authenticated page editor, which meaningfully narrows the attacker population to insiders or anyone who has compromised an editor account. Impact is confidentiality-only (VC:H, with VI/VA:N), consistent with CWE-200 and the description's exposure of configuration, request metadata, and database queries via the Clockwork profiler. No EPSS score, CISA KEV listing, SSVC decision, or POC indicator is present in the input, so there is no signal of active exploitation or automatable mass-scanning; the realistic risk is targeted abuse by a malicious or compromised low-privileged editor rather than widespread opportunistic attacks. No conflicting signals were observed between the CVSS vector and the description - both point to authenticated, remote, confidentiality-only disclosure. |
| Exploit ScenarioDerived | An attacker who holds (or has phished) a Grav page-editor account authors a page containing Twig that renders the omitted system.debugger.token value, which the sandbox redaction list fails to hide. They then replay that token in an X-Clockwork-Auth header to pull Clockwork profiler records, harvesting application configuration, request metadata, and raw database queries. No public exploit code was identified at time of analysis, and exploitation requires an authenticated editor, limiting it to insiders or account-takeover situations. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Page editors on Grav CMS versions 2.0.22 through 2.1.6 can render the Clockwork debugger's system.debugger.token via editor-authored Twig and replay it as the X-Clockwork-Auth header, disclosing profiler records that contain configuration values, request metadata, and database queries. The flaw is an authenticated, page-editor-level information disclosure (CVSS 4.0 base 7.1; independent assessment CVSS 3.1 AV:N/AC:L/PR:L/UI:N/C:H/I:N/A:N) that requires the Clockwork debugger to be enabled so that a token and profiler records exist; it is not anonymously reachable. Exploitation status: no public exploit identified at time of analysis, and the issue is remediated by upgrading to 2.1.7, which adds system.debugger.token to the Twig sandbox redaction list. This is a moderate-priority information disclosure flaw, not a critical emergency, because it needs valid editor credentials and Twig authoring rights and yields read-only exposure.
RemediationAI
Upgrade Grav CMS to 2.1.7 or later, the vendor-released patch that adds system.debugger.token to the Twig sandbox redaction list and closes the leak; the fix is documented in GHSA-5qv7-9gjc-4vfh (https://github.com/getgrav/grav/security/advisories/GHSA-5qv7-9gjc-4vfh) and in the VulnCheck advisory (https://www.vulncheck.com/advisories/grav-2.0.22-before-2.1.7-clockwork-debugger-token-disclosure-via-twig-sandbox). If upgrading cannot be done immediately, disable the Clockwork debugger on all internet-facing or non-development installs so that no token or profiler records exist to steal, accepting the trade-off that profiling data is unavailable for troubleshooting; rotate system.debugger.token after any suspected exposure so previously captured tokens can no longer retrieve profiler records; reduce the affected principal set by auditing which accounts hold page-editor or Twig-authoring rights and removing the capability from users who do not need it, noting this is only a partial control because legitimate editors remain able to exploit the flaw; and, where Clockwork is genuinely required, block or strip the X-Clockwork-Auth header at the reverse proxy or WAF so externally supplied tokens cannot authenticate against the debug endpoint, with the trade-off that legitimate remote Clockwork clients will need a bypass path.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Grav is a flat-file PHP content management system in which pages can embed Twig templates, and Grav ships a Twig sandbox that strips or redacts sensitive variables before editor-supplied templates are evaluated. CVE-2026-109315 is a CWE-200 exposure of sensitive information caused by an incomplete redaction list: the sandbox removes other sensitive entries but omits system.debugger.token, so a page editor who can author Twig can dereference the value and have it rendered into page output. That token is the shared secret the Clockwork debugger uses to authenticate retrieval of profiler records, which is why it can be supplied as the X-Clockwork-Auth header to pull stored profiler data. The profiler records themselves are the secondary exposure surface, since Clockwork captures configuration, request metadata, and database queries, turning a token leak into a much broader disclosure. Per the CPE cpe:2.3:a:getgrav:grav:*:*:*:*:*:*:*:* the affected codebase is Grav itself rather than a plugin, and the prerequisite state is an installation running the vulnerable version range with the debugger active, which in practice usually means a non-production or debug-enabled configuration.
Know when Grav gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Remote low-complexity disclosure needing an authenticated editor (PR:L), no user interaction, confidentiality-only impact (config/DB queries) so C:H, I:N, A:N, scope unchanged.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
Grav from 2.0.22 before 2.1.7 contains an information disclosure vulnerability that allows page editors to read the Clockwork debugger token because the sandbox redaction list omits system.debugger.token. Attackers can render the token through editor-authored Twig and supply it as X-Clockwork-Auth to read profiler records with configuration, request metadata, and database queries.
Technical POC Analysis
CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Grav CMS versions 2.0.22 through 2.1.6 with the Clockwork debugger enabled expose authenticated page editors to information disclosure, allowing them to view profiler records containing configuration values, request metadata, and database queries. This is a read-only exposure requiring valid editor credentials and debugger activation, and no public exploit has been identified at time of analysis. Leadership should care because lower-privileged users may access sensitive operational details, though the risk is moderate and not an emergency.
Apply vendor patch (upgrade to 2.1.7); if the patch is not yet available, disable Clockwork debugger, restrict Twig authoring for page editors, rotate debugger tokens, and block X-Clockwork-Auth header at the reverse proxy.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Server-side template injection (SSTI) in Grav (getgrav/grav) prior to 1.8.0-beta.27 allows an authenticated attacker hol
Broken access control in Grav CMS (CWE-285) before 1.8.0-beta.27 lets an authenticated editor-level user escalate their
A Remote Code Execution (RCE) vulnerability in Grav CMS v1.7.48 allows an authenticated admin to upload a malicious plug
Grav is a file-based Web platform. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low a
GravCMS 1.10.7 allows unauthenticated remote attackers to write arbitrary YAML configuration files, leading to full serv
Remote code execution in Grav CMS 2.0.4 (fixed in 2.0.7) lets an authenticated user holding the admin.pages or api.pages
Remote code execution in Grav CMS before 2.0.15 allows attackers holding page-edit or blueprint-config privileges to wri
Vertical privilege escalation in Grav CMS before 2.0.14 lets a delegated administrator holding only the admin.users perm
Stored cross-site scripting in Grav CMS before 2.0.15 lets authenticated editors smuggle JavaScript event handlers past
Server-side request forgery (SSRF) in Grav CMS versions prior to 1.7.49.5 allows remote authenticated attackers to make
Grav is a file-based Web platform. Prior to 1.8.0-beta.27, Grav CMS is vulnerable to a Server-Side Template Injection (S
Remote code execution in Grav CMS before 2.0.13 allows authenticated low-privilege users to plant and execute arbitrary
EUVD-2026-97617
GHSA-r6g3-r4xj-3p43
NVD
CVE.org
EPSS
Exploit-DB