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.
CVE-2026-97637
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-02. A secondary CVSS source baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALhigh confidence
- EG Risk
- 59EG Risk 59/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation1% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.6%
- EPSS %ILE
- 48th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 2, 2026
Last Modified
October 3, 2026
References (7)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/json-api-auth/tags/3.1.2/controllers/Auth.php#L104
- security@wordfencehttps://plugins.trac.wordpress.org/browser/json-api-auth/tags/3.1.2/controllers/Auth.php#L28
- security@wordfencehttps://plugins.trac.wordpress.org/browser/json-api-auth/tags/3.1.2/controllers/Auth.php#L66
- security@wordfencehttps://plugins.trac.wordpress.org/browser/json-api-auth/tags/3.1.2/controllers/Auth.php#L77
- security@wordfencehttps://plugins.trac.wordpress.org/browser/json-api-auth/tags/3.1.2/json-api-auth.php#L65
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3712939%40json-api-auth&new=3712939%40json-api-auth
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/f2fdf8bf-7f53-4579-9a1f-be7b3ef1ca50?source=cve
Vendor Advisories for CVE-2026-97637(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 24× in last 7d / 24× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 13:04 UTCGHSA enrichment
- 2026-10-04 08:55 UTCGHSA enrichment
- 2026-10-04 04:46 UTCGHSA enrichment
- 2026-10-04 00:38 UTCGHSA enrichment
- 2026-10-03 20:30 UTCGHSA enrichment
- 2026-10-03 16:23 UTCEG score recompute
- 2026-10-03 16:23 UTCGHSA enrichment
- 2026-10-03 16:11 UTCEG score recompute
- 2026-10-03 16:11 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 14:10 UTCGHSA enrichment
- 2026-10-03 10:02 UTCGHSA enrichment
- 2026-10-03 05:54 UTCGHSA enrichment
- 2026-10-03 01:46 UTCGHSA enrichment
- 2026-10-02 21:38 UTCEG score recompute
- 2026-10-02 21:38 UTCGHSA enrichment
- 2026-10-02 17:57 UTCEPSS rescore
- 2026-10-02 17:30 UTCGHSA enrichment
- 2026-10-02 13:23 UTCGHSA enrichment
- 2026-10-02 12:35 UTCEG score recompute
- 2026-10-02 12:35 UTCGHSA enrichment
- 2026-10-02 08:27 UTCEG score recompute
- 2026-10-02 07:46 UTCEG score recompute
- 2026-10-02 07:45 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-97637?
When was CVE-2026-97637 disclosed?
Is CVE-2026-97637 actively exploited?
What is the CVSS score of CVE-2026-97637?
How do I remediate CVE-2026-97637?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-97637
Is Your Infrastructure Affected by CVE-2026-97637?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.