Skip to main content
VulnerabilityPublished Updated

CVE-2026-62667: getgrav grav-plugin-api · Missing Authorization

Affects getgrav grav-plugin-apiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 1.0.6 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 grav-plugin-api and getgrav/grav-plugin-api to 1.0.6.

Affected software

ProductAffectedFixed in
getgravgrav-plugin-apiAffected
  • <1.0.6
Fixed in
  • 1.0.6
GitHubgetgrav/grav-plugin-apipkg:github/getgrav/grav-plugin-apiOther threatsAffected
  • <1.0.6
Fixed in
  • 1.0.6

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.6 or later, where this authorization issue is fixed. No other mitigation is required as the fix is official and addresses the root cause.

Description

CVE-2026-62667 is a missing authorization vulnerability in the Grav API Plugin for Grav CMS versions prior to 1.0.6. The flaw allows an API key issued with limited scopes to bypass scope restrictions and perform all actions available to the owning user, including write, delete, and administrative operations. This occurs because the authentication process does not properly enforce declared scopes, leading to excessive permissions. The issue is fixed in version 1.0.6.

References

Community reviews

Loading reviews…