CVE-2026-97637

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
59
EG 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 computed
Severity98% × 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

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.

  1. 2026-10-04 13:04 UTCGHSA enrichment
  2. 2026-10-04 08:55 UTCGHSA enrichment
  3. 2026-10-04 04:46 UTCGHSA enrichment
  4. 2026-10-04 00:38 UTCGHSA enrichment
  5. 2026-10-03 20:30 UTCGHSA enrichment
  6. 2026-10-03 16:23 UTCEG score recompute
  7. 2026-10-03 16:23 UTCGHSA enrichment
  8. 2026-10-03 16:11 UTCEG score recompute
  9. 2026-10-03 16:11 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 14:10 UTCGHSA enrichment
  12. 2026-10-03 10:02 UTCGHSA enrichment
  13. 2026-10-03 05:54 UTCGHSA enrichment
  14. 2026-10-03 01:46 UTCGHSA enrichment
  15. 2026-10-02 21:38 UTCEG score recompute
  16. 2026-10-02 21:38 UTCGHSA enrichment
  17. 2026-10-02 17:57 UTCEPSS rescore
  18. 2026-10-02 17:30 UTCGHSA enrichment
  19. 2026-10-02 13:23 UTCGHSA enrichment
  20. 2026-10-02 12:35 UTCEG score recompute
  21. 2026-10-02 12:35 UTCGHSA enrichment
  22. 2026-10-02 08:27 UTCEG score recompute
  23. 2026-10-02 07:46 UTCEG score recompute
  24. 2026-10-02 07:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97637?
CVE-2026-97637 is a critical vulnerability published on October 2, 2026. 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…
When was CVE-2026-97637 disclosed?
CVE-2026-97637 was first published on October 2, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97637 actively exploited?
CVE-2026-97637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97637?
CVE-2026-97637 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97637?
No fix for CVE-2026-97637 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97637 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-97637

Explore →

Is Your Infrastructure Affected by CVE-2026-97637?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.