CVE-2026-63408: getgrav grav-plugin-api · Use of GET Request Method With Sensitive Query Strings
Affects getgrav grav-plugin-apiSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 1.0.0-rc.16 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.0-rc.16
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade getgrav grav-plugin-api to 1.0.0-rc.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| getgravgrav-plugin-api | Affected
| Fixed in
|
GitHubgetgrav/grav-plugin-apipkg:github/getgrav/grav-plugin-apiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.