CVE-2026-62386: Use of GET Request Method With Sensitive Query Strings in getgrav grav
The Grav API plugin (getgrav/grav-plugin-api) before 1.0.0-rc.16 accepts JWT access tokens through the ?token= URL query parameter on every API route (JwtAuthenticator::extractBearerToken fallback). Because tokens are embedded in URLs, they are logged verbatim in web server access logs, leaked via the Referer header, stored in browser history, and captured by upstream proxy and CDN logs, exposing valid admin access tokens. A leaked token grants unauthorized API access, including reading configuration and user data, creating admin accounts, modifying system settings, and deleting pages.
AI Analysis
Technical Summary
CVE-2026-62386 describes a vulnerability in the Grav API plugin before version 1.0.0-rc.16 where JWT access tokens are accepted through the ?token= URL query parameter on every API route. Because tokens are embedded in URLs, they are exposed in multiple locations including web server access logs, Referer headers, browser history, and upstream proxy or CDN logs. This exposure can lead to leakage of valid admin access tokens. Possession of such a token allows unauthorized API access with high privileges, including reading sensitive data, creating admin accounts, changing system settings, and deleting content.
Potential Impact
The vulnerability allows attackers who obtain leaked JWT tokens to gain unauthorized administrative access to the Grav API. This includes the ability to read configuration and user data, create new admin accounts, modify system settings, and delete pages. The exposure of tokens in logs and headers significantly increases the risk of token theft and subsequent compromise of the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid passing JWT tokens via URL query parameters. Use alternative methods such as Authorization headers to transmit tokens securely. Review and restrict access to logs and proxies that may capture sensitive URL data to minimize token exposure.
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 1.0.0-rc.16 accepts JWT access tokens through the ?token= URL query parameter on every API route (JwtAuthenticator::extractBearerToken fallback). Because tokens are embedded in URLs, they are logged verbatim in web server access logs, leaked via the Referer header, stored in browser history, and captured by upstream proxy and CDN logs, exposing valid admin access tokens. A leaked token grants unauthorized API access, including reading configuration and user data, creating admin accounts, modifying system settings, and deleting pages.
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 describes a vulnerability in the Grav API plugin before version 1.0.0-rc.16 where JWT access tokens are accepted through the ?token= URL query parameter on every API route. Because tokens are embedded in URLs, they are exposed in multiple locations including web server access logs, Referer headers, browser history, and upstream proxy or CDN logs. This exposure can lead to leakage of valid admin access tokens. Possession of such a token allows unauthorized API access with high privileges, including reading sensitive data, creating admin accounts, changing system settings, and deleting content.
Potential Impact
The vulnerability allows attackers who obtain leaked JWT tokens to gain unauthorized administrative access to the Grav API. This includes the ability to read configuration and user data, create new admin accounts, modify system settings, and delete pages. The exposure of tokens in logs and headers significantly increases the risk of token theft and subsequent compromise of the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid passing JWT tokens via URL query parameters. Use alternative methods such as Authorization headers to transmit tokens securely. Review and restrict access to logs and proxies that may capture sensitive URL data to minimize token exposure.
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/24/2026, 21:48:10 UTC
Last updated: 08/30/2026, 10:52:10 UTC
Views: 94
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.