CVE-2026-63408: CWE-598: Use of GET Request Method With Sensitive Query Strings in getgrav grav-plugin-api
Grav API Plugin is a RESTful API for Grav CMS that provides full headless access to your site's content. Prior to 1.0.0-rc.16, the Grav API plugin JwtAuthenticator::extractBearerToken() accepts a JWT from the token URL query parameter on every /api/v1 route, including state-changing endpoints. Request URLs consequently expose valid access tokens through Apache, proxy, and CDN logs, browser history, and Referer headers, allowing a party with access to those records to reuse the token with the owner's API privileges. This issue is fixed in version 1.0.0-rc.16.
AI Analysis
Technical Summary
CVE-2026-63408 describes a vulnerability in the Grav API Plugin where the JwtAuthenticator::extractBearerToken() method accepts JWT tokens passed as URL query parameters on all /api/v1 endpoints, including state-changing ones. This practice leads to sensitive tokens being exposed in logs and browser histories, increasing the risk of token theft and unauthorized API access. The vulnerability is fixed starting from version 1.0.0-rc.16.
Potential Impact
Exposure of valid JWT access tokens in URLs allows attackers with access to logs or browser histories to reuse these tokens and perform API actions with the privileges of the token owner. This can lead to unauthorized access to sensitive content or operations within the Grav CMS environment. The CVSS score of 7.5 (high) reflects the network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact.
Mitigation Recommendations
Upgrade to Grav API Plugin version 1.0.0-rc.16 or later, where the vulnerability is fixed by no longer accepting JWT tokens via URL query parameters on state-changing API routes. Until upgrading, avoid passing JWT tokens in URL query strings to reduce exposure in logs and browser histories.
CVE-2026-63408: CWE-598: Use of GET Request Method With Sensitive Query Strings in getgrav grav-plugin-api
Description
Grav API Plugin is a RESTful API for Grav CMS that provides full headless access to your site's content. Prior to 1.0.0-rc.16, the Grav API plugin JwtAuthenticator::extractBearerToken() accepts a JWT from the token URL query parameter on every /api/v1 route, including state-changing endpoints. Request URLs consequently expose valid access tokens through Apache, proxy, and CDN logs, browser history, and Referer headers, allowing a party with access to those records to reuse the token with the owner's API privileges. This issue is fixed in version 1.0.0-rc.16.
CVSS v3.1
Score 7.5high
Affected software
pkg:github/getgrav/grav-plugin-apiRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-63408 describes a vulnerability in the Grav API Plugin where the JwtAuthenticator::extractBearerToken() method accepts JWT tokens passed as URL query parameters on all /api/v1 endpoints, including state-changing ones. This practice leads to sensitive tokens being exposed in logs and browser histories, increasing the risk of token theft and unauthorized API access. The vulnerability is fixed starting from version 1.0.0-rc.16.
Potential Impact
Exposure of valid JWT access tokens in URLs allows attackers with access to logs or browser histories to reuse these tokens and perform API actions with the privileges of the token owner. This can lead to unauthorized access to sensitive content or operations within the Grav CMS environment. The CVSS score of 7.5 (high) reflects the network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact.
Mitigation Recommendations
Upgrade to Grav API Plugin version 1.0.0-rc.16 or later, where the vulnerability is fixed by no longer accepting JWT tokens via URL query parameters on state-changing API routes. Until upgrading, avoid passing JWT tokens in URL query strings to reduce exposure in logs and browser histories.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-16T19:20:28.987Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a85d4edacd9273b494d33ca
Added to database: 08/19/2026, 16:08:13 UTC
Last enriched: 08/19/2026, 16:22:24 UTC
Last updated: 08/19/2026, 18:23:05 UTC
Views: 6
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.