CVE-2026-97637 — WordPress
CRITICALCVE-2026-97637 is a critical-severity (CVSS 9.8) Improper Authentication vulnerability. No vendor fix is recorded yet; mitigation options are listed below.
The JSON API Auth plugin for WordPress is vulnerable to Authentication Bypass via Cached Session Cookie Disclosure in all versions up to, and including, 3.1.2. The vulnerability exists…
Description
The JSON API Auth plugin for WordPress is vulnerable to Authentication Bypass via Cached Session Cookie Disclosure in all versions up to, and including, 3.1.2. The vulnerability exists because the required PI-Media/json-api parent plugin caches controller dispatch results in transients keyed solely by URI and query string, ignoring HTTP method and POST body; this causes the generate_auth_cookie() endpoint — which embeds a live WordPress logged_in cookie produced by wp_generate_auth_cookie() directly in its JSON response body — to serve that cached authenticated response to any subsequent unauthenticated GET request to the same URI. This makes it possible for unauthenticated attackers to retrieve a valid Administrator logged_in session cookie from the cached response and use it to fully authenticate as the site Administrator, including via the same plugin's get_currentuserinfo endpoint and any cookie-authenticated controller action. Exploitation requires the PI-Media/json-api parent plugin to be installed and active with the Auth controller enabled, and a legitimate Administrator must have POSTed to /api/auth/generate_auth_cookie/ within the preceding 24-hour cache TTL; the nominal HTTPS enforcement gate present in Auth.php is trivially bypassed by supplying insecure=cool as a request parameter.
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-97637 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-97637 in your dependencies?
Find it across , including transitive dependencies.