dbcve.org
CWE-613Weakness · CWE-613

CVE-2026-61452

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Grav API plugin (getgrav/grav-plugin-api) before 2.0.4 contains an improper session invalidation vulnerability where JWT access tokens are issued without a jti (JWT ID) claim and therefore cannot be revoked server-side. Unlike refresh tokens, access tokens remain valid for their full lifetime (default 1 hour) regardless of logout, password change, new token issuance, or account disablement. An attacker who has stolen an access token retains full API access until the token naturally expires.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Grav API plugin issues JWT access tokens without a jti (JWT ID) claim, making them non-revocable server-side. Since access tokens (default 1-hour lifetime) lack a unique identifier, there is no mechanism to invalidate them upon logout, password change, or account disablement. An attacker with a stolen token retains full API access until natural expiration.

MitigationAdd a unique jti claim to JWT access tokens and implement server-side token revocation via a blacklist or by storing token jti/jwtid against the user session, combined with shorter token lifetimes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Grav CMS installation
    Identify the Grav installation path and check for the presence of the Grav core files (index.php or system/src/Grav). Determine the installed Grav version by examining the version file or composer.json in the root directory.
    Affected if Grav CMS is not installed or the version is unknown, the vulnerability does not apply.
  2. Locate the API plugin
    Navigate to the Grav plugins directory (user/plugins/ or system/plugins/) and check for the presence of an 'api' or 'api-plugin' directory. List all installed plugins to identify API-related functionality.
    Affected if The API plugin is not installed, the vulnerability does not apply to this environment.
  3. Verify API plugin is enabled
    Check the plugin configuration file (user/plugins/api/plugins.yaml or similar) for an 'enabled: true' setting, or query the Grav admin panel if available to confirm the API plugin status.
    Affected if The API plugin is installed but disabled, the vulnerability may not be exploitable.
  4. Inspect JWT configuration
    Examine the API plugin configuration files (user/plugins/api/config.yaml or similar) for JWT-related settings such as jwt_secret, token_lifetime, or any token generation code. Look for whether a jti or jwtid parameter is defined in the token generation logic.
    Affected if JWT tokens are generated without a jti claim in the configuration or code.
  5. Analyze token issuance code
    Review the PHP source files in the API plugin that handle token generation (typically files containing 'jwt', 'token', or 'oauth' in the filename). Search for the JWT payload construction to verify if the jti field is included in the token claims.
    Affected if The code generates JWT tokens without a jti (JWT ID) claim in the payload.

A user is affected if Grav CMS with the API plugin is installed, enabled, and the plugin generates JWT access tokens that lack a jti (JWT ID) claim, preventing server-side token revocation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add a unique jti claim to JWT access tokens and implement server-side token revocation via a blacklist or by storing token jti/jwtid against the user session, combined with shorter token lifetimes.

Recommended fix High confidence

2.0.4 or later

  1. Upgrade the Grav API plugin (getgrav/grav-plugin-api) to version 2.0.4 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61452 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-61452 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data