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

New CVE Detected

CVE-2026-58656 – Cross-Origin Admin Account Takeover via JWT Leakage and CORS Misconfiguration – …

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

Summary

CVE-2026-58656 is a high-severity vulnerability in the Grav CMS API plugin (getgrav/grav-plugin-api) affecting all versions before v1.0.0-rc.16, carrying a CVSS 4.0 score of 8.7 (High). The flaw combines two compounding weaknesses — the plugin exposes JWT authentication tokens via the ?token= URL query parameter, leaking credentials into server access logs, browser history, and HTTP Referrer headers; and every API response includes a wildcard Access-Control-Allow-Origin: * header, permitting any website to read authenticated API responses from a browser context. An attacker who obtains a leaked JWT token through any of these side channels can make fully authenticated cross-origin API calls, create persistent backdoor super-admin accounts, and exfiltrate sensitive configuration and user data from the affected Grav installation.

Technical details

  • Root cause (1) — CWE-598: The JwtAuthenticator::extractBearerToken() method accepts JWT authentication tokens via the ?token= URL query parameter across all API endpoints. This causes tokens to appear in web server and CDN access logs, upstream proxy logs, browser history, and HTTP Referrer headers forwarded to third-party sites during normal navigation.
  • Root cause (2) — CWE-942: Every API response is served with the header Access-Control-Allow-Origin: *. Because the token is delivered as a URL parameter rather than a credential-bearing HTTP header, the browser’s CORS credential-blocking protections do not apply, allowing JavaScript on any origin to read the full authenticated API response.
  • Attack chain: An attacker obtains a leaked JWT token from one of the above side channels, then crafts a malicious webpage embedding a fetch() request to the target Grav API with the token in the URL. The browser executes the cross-origin request and reads the response, enabling arbitrary authenticated API operations without any interaction from a logged-in user.
  • Impact: Creation of persistent backdoor super-admin accounts; exfiltration of admin profiles, system configuration data, and user data; arbitrary content deletion. Backdoor accounts persist independently of subsequent JWT token rotation.

Affected software

  • getgrav/grav-plugin-api — all versions prior to v1.0.0-rc.16

Severity

  • CVSS 4.0: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS 3.1: 7.5 (High) — 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 v1.0.0-rc.16 or later. The patch removes query-parameter token extraction and replaces the wildcard CORS policy with explicit domain allowlisting, enforcing token delivery exclusively via the Authorization or X-API-Token HTTP headers.
  • Post-upgrade: Audit all web server, proxy, and CDN access logs for JWT tokens exposed in URL query strings; rotate all existing JWT tokens; review Grav user accounts for any unauthorized super-admin accounts.
  • If immediate patching is not feasible: Restrict network-level access to the Grav API endpoints (e.g., via firewall rules or web server ACLs) to explicitly trusted IP ranges only, to limit the pool of potential token recipients.

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