CVE-2026-58656: Use of GET Request Method With Sensitive Query Strings in getgrav grav
Grav API plugin before v1.0.0-rc.16 accepts JWT tokens via the ?token= URL query parameter and responds with Access-Control-Allow-Origin: *, allowing unauthenticated attackers to make fully authenticated cross-origin API requests from any malicious website. Attackers who obtain a leaked JWT token from access logs, proxy logs, browser history, or Referrer headers can create persistent backdoor super-admin accounts and exfiltrate sensitive configuration and user data.
AI Analysis
Technical Summary
The Grav API plugin prior to version 1.0.0-rc.16 has a vulnerability where it accepts JWT tokens through the GET request query string parameter 'token' and responds with a permissive CORS header (Access-Control-Allow-Origin: *). This allows unauthenticated attackers to make fully authenticated cross-origin API requests from any malicious website if they can obtain a JWT token leaked in access logs, proxy logs, browser history, or Referrer headers. Exploitation can lead to creation of persistent backdoor super-admin accounts and exfiltration of sensitive configuration and user data.
Potential Impact
An attacker who obtains a leaked JWT token can bypass authentication and perform privileged actions on the Grav API, including creating super-admin accounts and accessing sensitive configuration and user data. The vulnerability enables cross-origin requests from any origin due to the permissive CORS policy, increasing the risk of token theft and unauthorized access.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should avoid exposing JWT tokens in URL query parameters and monitor for vendor updates addressing this vulnerability. Until an official fix is available, consider restricting CORS policies and reviewing access logs for token leakage.
CVE-2026-58656: Use of GET Request Method With Sensitive Query Strings in getgrav grav
Description
Grav API plugin before v1.0.0-rc.16 accepts JWT tokens via the ?token= URL query parameter and responds with Access-Control-Allow-Origin: *, allowing unauthenticated attackers to make fully authenticated cross-origin API requests from any malicious website. Attackers who obtain a leaked JWT token from access logs, proxy logs, browser history, or Referrer headers can create persistent backdoor super-admin accounts and exfiltrate sensitive configuration and user data.
CVSS v4.0
Score 8.7high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Grav API plugin prior to version 1.0.0-rc.16 has a vulnerability where it accepts JWT tokens through the GET request query string parameter 'token' and responds with a permissive CORS header (Access-Control-Allow-Origin: *). This allows unauthenticated attackers to make fully authenticated cross-origin API requests from any malicious website if they can obtain a JWT token leaked in access logs, proxy logs, browser history, or Referrer headers. Exploitation can lead to creation of persistent backdoor super-admin accounts and exfiltration of sensitive configuration and user data.
Potential Impact
An attacker who obtains a leaked JWT token can bypass authentication and perform privileged actions on the Grav API, including creating super-admin accounts and accessing sensitive configuration and user data. The vulnerability enables cross-origin requests from any origin due to the permissive CORS policy, increasing the risk of token theft and unauthorized access.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should avoid exposing JWT tokens in URL query parameters and monitor for vendor updates addressing this vulnerability. Until an official fix is available, consider restricting CORS policies and reviewing access logs for token leakage.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-01T21:54:37.946Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4e5b32c9d9e3dbe33e52dd
Added to database: 07/08/2026, 14:14:10 UTC
Last enriched: 07/08/2026, 14:28:12 UTC
Last updated: 08/22/2026, 10:52:10 UTC
Views: 77
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.