Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-62386 – JWT Admin Token Leakage via URL Parameter – Grav API Plugin before 1.0.0-rc.16

Be the first to know when new zero-days emerge:

Summary

CVE-2026-62386 is a high-severity vulnerability (CVSS 8.2) classified as CWE-598 (Use of GET Request Method With Sensitive Query Strings), affecting the Grav CMS API plugin (getgrav/grav-plugin-api) in all versions before 1.0.0-rc.16. The plugin’s JwtAuthenticator::extractBearerToken() method accepts JWT admin access tokens via the ?token= URL query parameter across every API route, causing valid tokens to be persistently logged and leaked through multiple channels. An attacker who obtains a leaked token gains full unauthorized administrative API access to the affected Grav installation.

Technical details

  • Root cause: The JwtAuthenticator::extractBearerToken() fallback method accepts JWT access tokens via the ?token= URL query parameter on every API endpoint, rather than restricting token acceptance to secure HTTP headers. Any API call made using the query parameter method embeds the admin token directly in the URL.
  • Trigger conditions: Any API request authenticated via the ?token= query parameter — whether issued by an authorized user, an API client, or a frontend application — exposes the JWT token through standard HTTP infrastructure: it is logged verbatim in web server access logs, transmitted in the HTTP Referer header to third-party sites, stored in browser history, and captured by upstream proxy and CDN logs.
  • Attack vector: Network-accessible. An attacker with access to any of the above log sources or intermediary infrastructure can extract a valid admin token and replay it to make fully authenticated API calls without ever possessing the original credentials. The CVSS 4.0 vector reflects AT:P (Attack Requirements: Present) due to this indirect dependency.
  • Impact: A leaked token grants complete administrative API access, including reading system configuration and user data, creating new admin accounts, modifying system settings, and deleting pages — effectively constituting a full site compromise.

Affected software

  • getgrav/grav-plugin-api all versions from 0 through v1.0.0-rc.15 (all versions before 1.0.0-rc.16)

Severity

CVSS v3.1 base score: 7.5 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade the Grav API plugin to version 1.0.0-rc.16 or later. This release removes ?token= query parameter token acceptance and restricts JWT authentication exclusively to the Authorization: Bearer and X-API-Token HTTP headers.
  • If immediate patching is not possible: Disable or restrict external access to the API plugin routes (default path: /api/v1/) at the web server or network perimeter level. Additionally, audit existing web server access logs, proxy logs, and CDN logs for any occurrences of ?token= in API request URLs, and immediately revoke any JWT tokens found to be exposed.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge