CVE-2026-63407: getgrav grav-plugin-api · Permissive Cross-domain Policy with Untrusted Domains
Affects getgrav grav-plugin-apiSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 1.0.0-rc.16 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% 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:R/S:C/C:H/I:L/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 15 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 the Grav API Plugin to version 1.0.0-rc.16 or later, where the permissive CORS policy issue is fixed. No other mitigation is required once the plugin is updated.
Description
CVE-2026-63407 is a high-severity vulnerability in the Grav API Plugin for Grav CMS. Prior to version 1.0.0-rc.16, the plugin's CORS middleware allowed any origin to access authenticated API endpoints by returning Access-Control-Allow-Origin: *. This permissive cross-domain policy enables JavaScript from any origin to submit attacker-obtained JWT tokens and perform actions with the token owner's privileges, including reading data and modifying accounts. The issue is fixed in version 1.0.0-rc.16.