Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-92916 – Unauthenticated Session Hijack & Credential Disclosure – Grav 1.7.0–1.7.53.2 and 2.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-92916 is an unauthenticated information disclosure vulnerability in Grav CMS caused by the Clockwork debugging profiler being exposed without any authentication when the debugger is enabled. The exposed /__clockwork/ endpoint discloses session cookies, plaintext login credentials, and full system/plugin configuration (including API keys and other secrets), allowing a remote, unauthenticated attacker to hijack authenticated sessions — including administrator sessions — and harvest sensitive credentials. The issue affects Grav and carries a CVSS v4.0 base score of 8.7 (High).

Technical details

  • Root cause: When Grav’s debugger is enabled, it exposes the Clockwork profiler endpoint (/__clockwork/) without requiring authentication. Clockwork records are stored as plaintext JSON in cache/clockwork/ and are readable through this endpoint by any visitor.
  • Sensitive data exposed: Recorded data includes raw request cookies — including Grav’s session cookie (the PHP session ID), which can be replayed to resume another user’s session, including an authenticated admin’s — the full parsed request body, and the site’s complete system and plugin configuration, including operator-configured secrets such as SMTP credentials, third-party API keys, and license keys.
  • Login credential leakage: Because Grav’s login form submits data as data[username]/data[password], Clockwork’s password-censoring filter — which only inspects top-level request keys — fails to redact these nested fields, so passwords are stored and exposed in plaintext.
  • Additional exposure regardless of settings: Authorization and X-API-Token headers are recorded even when the censored: true option is set. On Grav 2.0, configuring provider: debugbar does not prevent exposure because Grav forces use of the Clockwork provider for requests that prefer a JSON response.
  • Attack vector: Network-based; the endpoint can be reached directly over HTTP with no authentication, and no user interaction is required.
  • Impact: Session hijacking (including administrator account takeover) and disclosure of credentials and secrets stored in site configuration.

Affected software

  • Grav versions 1.7.0 through 1.7.53.2
  • Grav versions 2.0.0 through 2.0.21

Severity

  • CVSS v4.0 Base Score: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Grav 1.7.53.4 or 2.0.22 (or later), which restrict /__clockwork/ to server-local requests or requests presenting a new system.debugger.token secret, and which strip sensitive cookies and credentials from stored records.
  • If patching is not immediately possible:
    • Disable the debugger entirely by setting debugger.enabled: false in the Grav configuration.
    • Block access to /__clockwork/ paths at the web server or CDN/edge level.
    • Run bin/grav clear to purge any previously recorded profiler data containing sensitive information from cache/clockwork/.
    • Rotate any credentials, API keys, or session-derived secrets that may have already been exposed via the endpoint.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge