CVE-2026-92916
Last modified
CVE-2026-92916 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. Grav is a flat-file CMS. In Grav 1.7.0 through 1.7.53.2 and 2.0.0 through 2.0.21, when the debugger is enabled (system.debugger.enabled: true, which is not the default), the Clockwork profiler endpoint is exposed without authentication: InitializeProcessor::handleDebuggerRequest() intercepts any path containing /__clockwork/ during bootstrap and passes it to Debugger::debuggerRequest(), which performs no user lookup, IP restriction, or Clockwork authenticator check, and also supports anonymous pagination over the entire stored history.
Description
Grav is a flat-file CMS. In Grav 1.7.0 through 1.7.53.2 and 2.0.0 through 2.0.21, when the debugger is enabled (system.debugger.enabled: true, which is not the default), the Clockwork profiler endpoint is exposed without authentication: InitializeProcessor::handleDebuggerRequest() intercepts any path containing /__clockwork/ during bootstrap and passes it to Debugger::debuggerRequest(), which performs no user lookup, IP restriction, or Clockwork authenticator check, and also supports anonymous pagination over the entire stored history. With the shipped censored: false default, each stored record contains raw request cookies (including Grav's session cookie, whose value is the PHP session id, allowing an attacker to resume another user's session, including an authenticated admin's), the full parsed request body (Grav's login form posts data[username]/data[password], so passwords are stored in plaintext because Clockwork's password filter only inspects top-level keys), and the site's entire system and plugin configuration, including operator-saved secrets such as SMTP credentials, third-party API keys, and licence keys. Authorization and X-API-Token headers are stored even when censored: true. On Grav 2.0, setting provider: debugbar does not avoid the issue because Grav forces the Clockwork provider for requests preferring a JSON response. The issue is fixed in 1.7.53.4 and 2.0.22, which restrict /__clockwork/ to server-local requests or requests presenting the new system.debugger.token secret and strip cookies and credential headers from stored records. Workarounds include setting debugger.enabled: false or blocking /__clockwork/ at the web server or CDN.
Metrics
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-92916?
How severe is CVE-2026-92916?
How do I fix CVE-2026-92916?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-92904A flaw was found in the foreman_remote_execution plugin's te…4.3
- CVE-2026-9291Insecure deserialization in the job results processing compo…7.5
- CVE-2026-92912AVideo through c3edcc274c389816d434acadac07ee78eaf330c1 uses…6.5
- CVE-2026-92913AVideo through commit c3edcc274c389816d434acadac07ee78eaf330…7.4
- CVE-2026-92914AVideo LoginControl contains an authentication bypass vulner…8.1
- CVE-2026-92915WWBN AVideo through commit e01e41ecc (no patched version ava…7.3
- CVE-2026-92917Grav is a flat-file CMS. In versions 2.0.0-rc.1 through 2.0.…7.5
- CVE-2026-92918admin3 through 3.0.0 persists user session tokens in the aud…8.8
- CVE-2026-92919admin3 through 3.0.0 fails to sanitize client-supplied filen…8.1
- CVE-2026-9292A Stored Cross-Site Scripting security issue exists within F…8.4
- CVE-2026-92920admin3 through 3.0.0 fails to invalidate existing sessions w…5.4
- CVE-2026-92921admin3 through 3.0.0 stores account passwords using single-r…4.9
Are you affected by CVE-2026-92916?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
