CVE-2026-62386: Use of GET Request Method With Sensitive Query Strings in getgrav grav
The Grav API plugin (getgrav/grav-plugin-api) before version 1.0.0-rc.16 accepts JWT access tokens via the URL query parameter ?token= on all API routes. This practice exposes tokens in web server logs, Referer headers, browser history, and proxy/CDN logs, risking token leakage. A leaked token allows unauthorized API access, including reading sensitive data, creating admin accounts, modifying settings, and deleting pages. The vulnerability has a high severity score of 8.2. No official patch or remediation guidance is currently provided.
AI Analysis
Technical Summary
CVE-2026-62386 affects the Grav API plugin prior to version 1.0.0-rc.16 by accepting JWT tokens through the ?token= query parameter on every API route. Embedding tokens in URLs leads to their exposure in various logs and browser artifacts, which can be exploited to gain unauthorized administrative API access. This includes the ability to read configuration and user data, create admin accounts, modify system settings, and delete pages. The vulnerability has a CVSS 4.0 score of 8.2 (high severity). No vendor advisory or patch information is available at this time.
Potential Impact
Exposure of JWT tokens in URLs results in their logging and leakage through multiple vectors such as web server access logs, Referer headers, browser history, and upstream proxy/CDN logs. An attacker obtaining a leaked token can perform unauthorized API actions with administrative privileges, including data disclosure, account creation, configuration changes, and content deletion.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using the ?token= query parameter to transmit JWT tokens. Prefer authorization headers or other secure token transmission methods to prevent token leakage via URLs.
CVE-2026-62386: Use of GET Request Method With Sensitive Query Strings in getgrav grav
Description
The Grav API plugin (getgrav/grav-plugin-api) before version 1.0.0-rc.16 accepts JWT access tokens via the URL query parameter ?token= on all API routes. This practice exposes tokens in web server logs, Referer headers, browser history, and proxy/CDN logs, risking token leakage. A leaked token allows unauthorized API access, including reading sensitive data, creating admin accounts, modifying settings, and deleting pages. The vulnerability has a high severity score of 8.2. No official patch or remediation guidance is currently provided.
CVSS v4.0
Score 8.2high
Affected software
Run 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
CVE-2026-62386 affects the Grav API plugin prior to version 1.0.0-rc.16 by accepting JWT tokens through the ?token= query parameter on every API route. Embedding tokens in URLs leads to their exposure in various logs and browser artifacts, which can be exploited to gain unauthorized administrative API access. This includes the ability to read configuration and user data, create admin accounts, modify system settings, and delete pages. The vulnerability has a CVSS 4.0 score of 8.2 (high severity). No vendor advisory or patch information is available at this time.
Potential Impact
Exposure of JWT tokens in URLs results in their logging and leakage through multiple vectors such as web server access logs, Referer headers, browser history, and upstream proxy/CDN logs. An attacker obtaining a leaked token can perform unauthorized API actions with administrative privileges, including data disclosure, account creation, configuration changes, and content deletion.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using the ?token= query parameter to transmit JWT tokens. Prefer authorization headers or other secure token transmission methods to prevent token leakage via URLs.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-13T22:40:54.412Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a59784368715ace4305da88
Added to database: 07/17/2026, 00:33:07 UTC
Last enriched: 07/17/2026, 00:47:36 UTC
Last updated: 07/17/2026, 01:27:30 UTC
Views: 5
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.