CVE-2026-13447

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-05. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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.4%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 Mstore Api plugin for WordPress is vulnerable to Authentication Bypass via JWT Forgery in versions up to, and including, 4.20.0 This is due to missing cryptographic signature verification in the FirebasePhoneAuthHelper::verify_id_token() function, which decodes and validates Firebase ID token claims (alg, kid, aud, iss) but never calls openssl_verify() or any equivalent to validate the JWT signature against Google's actual public key certificates. This makes it possible for unauthenticated attackers to forge a Firebase Phone Auth JWT signed with a self-generated RSA key pair and impersonate any phone number, resulting in unauthorized access to existing WordPress accounts or creation of new arbitrary accounts.

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%
Exploitation0% × 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.4%
EPSS %ILE
36th
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

September 5, 2026

Last Modified

September 8, 2026

Vendor Advisories for CVE-2026-13447(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 50× in last 7d / 222× 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.

Showing the most recent 100 of 222 total refreshes for this CVE.

  1. 2026-10-04 13:16 UTCGHSA enrichment
  2. 2026-10-04 09:01 UTCGHSA enrichment
  3. 2026-10-04 04:58 UTCGHSA enrichment
  4. 2026-10-04 00:56 UTCGHSA enrichment
  5. 2026-10-03 20:45 UTCGHSA enrichment
  6. 2026-10-03 16:33 UTCEG score recompute
  7. 2026-10-03 16:33 UTCGHSA enrichment
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 12:32 UTCGHSA enrichment
  10. 2026-10-03 06:14 UTCGHSA enrichment
  11. 2026-10-03 02:12 UTCGHSA enrichment
  12. 2026-10-02 22:11 UTCGHSA enrichment
  13. 2026-10-02 18:04 UTCEG score recompute
  14. 2026-10-02 18:04 UTCGHSA enrichment
  15. 2026-10-02 14:02 UTCGHSA enrichment
  16. 2026-10-02 10:00 UTCGHSA enrichment
  17. 2026-10-02 05:58 UTCGHSA enrichment
  18. 2026-10-02 01:34 UTCGHSA enrichment
  19. 2026-10-01 21:32 UTCEG score recompute
  20. 2026-10-01 21:32 UTCGHSA enrichment
  21. 2026-10-01 19:49 UTCEPSS rescore
  22. 2026-10-01 17:31 UTCGHSA enrichment
  23. 2026-10-01 13:10 UTCGHSA enrichment
  24. 2026-10-01 09:08 UTCGHSA enrichment
  25. 2026-10-01 05:07 UTCGHSA enrichment
Show 75 more
  1. 2026-10-01 00:53 UTCGHSA enrichment
  2. 2026-09-30 19:27 UTCGHSA enrichment
  3. 2026-09-30 15:25 UTCEG score recompute
  4. 2026-09-30 15:25 UTCGHSA enrichment
  5. 2026-09-30 15:02 UTCEPSS rescore
  6. 2026-09-30 11:18 UTCGHSA enrichment
  7. 2026-09-30 06:40 UTCGHSA enrichment
  8. 2026-09-30 02:38 UTCGHSA enrichment
  9. 2026-09-29 15:59 UTCEG score recompute
  10. 2026-09-29 15:59 UTCGHSA enrichment
  11. 2026-09-29 15:20 UTCEPSS rescore
  12. 2026-09-29 11:48 UTCGHSA enrichment
  13. 2026-09-29 07:18 UTCGHSA enrichment
  14. 2026-09-29 03:17 UTCGHSA enrichment
  15. 2026-09-28 23:13 UTCEG score recompute
  16. 2026-09-28 23:13 UTCGHSA enrichment
  17. 2026-09-28 19:07 UTCGHSA enrichment
  18. 2026-09-28 14:33 UTCEG score recompute
  19. 2026-09-28 14:33 UTCGHSA enrichment
  20. 2026-09-28 13:51 UTCEPSS rescore
  21. 2026-09-28 10:22 UTCGHSA enrichment
  22. 2026-09-28 06:21 UTCGHSA enrichment
  23. 2026-09-28 02:19 UTCGHSA enrichment
  24. 2026-09-27 22:18 UTCGHSA enrichment
  25. 2026-09-27 18:16 UTCGHSA enrichment
  26. 2026-09-27 14:15 UTCEG score recompute
  27. 2026-09-27 14:15 UTCGHSA enrichment
  28. 2026-09-27 10:06 UTCGHSA enrichment
  29. 2026-09-27 06:05 UTCGHSA enrichment
  30. 2026-09-27 02:02 UTCGHSA enrichment
  31. 2026-09-26 21:07 UTCGHSA enrichment
  32. 2026-09-26 17:05 UTCEG score recompute
  33. 2026-09-26 17:05 UTCGHSA enrichment
  34. 2026-09-26 15:58 UTCEPSS rescore
  35. 2026-09-26 12:20 UTCGHSA enrichment
  36. 2026-09-26 06:37 UTCGHSA enrichment
  37. 2026-09-26 01:44 UTCEG score recompute
  38. 2026-09-26 01:44 UTCGHSA enrichment
  39. 2026-09-25 16:18 UTCGHSA enrichment
  40. 2026-09-25 12:13 UTCGHSA enrichment
  41. 2026-09-25 08:11 UTCGHSA enrichment
  42. 2026-09-25 04:09 UTCGHSA enrichment
  43. 2026-09-25 00:08 UTCGHSA enrichment
  44. 2026-09-24 20:01 UTCGHSA enrichment
  45. 2026-09-24 15:59 UTCEG score recompute
  46. 2026-09-24 15:59 UTCGHSA enrichment
  47. 2026-09-24 11:58 UTCGHSA enrichment
  48. 2026-09-24 07:55 UTCGHSA enrichment
  49. 2026-09-24 03:54 UTCGHSA enrichment
  50. 2026-09-23 23:47 UTCGHSA enrichment
  51. 2026-09-23 19:45 UTCGHSA enrichment
  52. 2026-09-23 14:53 UTCEG score recompute
  53. 2026-09-23 14:53 UTCGHSA enrichment
  54. 2026-09-23 13:47 UTCEPSS rescore
  55. 2026-09-23 10:51 UTCGHSA enrichment
  56. 2026-09-23 06:50 UTCGHSA enrichment
  57. 2026-09-23 02:48 UTCGHSA enrichment
  58. 2026-09-22 22:46 UTCGHSA enrichment
  59. 2026-09-22 18:44 UTCEG score recompute
  60. 2026-09-22 18:44 UTCGHSA enrichment
  61. 2026-09-22 14:43 UTCGHSA enrichment
  62. 2026-09-22 10:41 UTCGHSA enrichment
  63. 2026-09-22 06:38 UTCGHSA enrichment
  64. 2026-09-22 02:37 UTCGHSA enrichment
  65. 2026-09-21 22:34 UTCEG score recompute
  66. 2026-09-21 22:34 UTCGHSA enrichment
  67. 2026-09-21 18:33 UTCGHSA enrichment
  68. 2026-09-21 14:31 UTCGHSA enrichment
  69. 2026-09-21 10:29 UTCGHSA enrichment
  70. 2026-09-21 06:27 UTCGHSA enrichment
  71. 2026-09-21 02:25 UTCGHSA enrichment
  72. 2026-09-20 22:23 UTCEG score recompute
  73. 2026-09-20 22:23 UTCGHSA enrichment
  74. 2026-09-20 20:15 UTCEPSS rescore
  75. 2026-09-20 18:21 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-13447?
CVE-2026-13447 is a critical vulnerability published on September 5, 2026. The Mstore Api plugin for WordPress is vulnerable to Authentication Bypass via JWT Forgery in versions up to, and including, 4.20.0 This is due to missing cryptographic signature verification in the FirebasePhoneAuthHelper::verifyidtoken() function, which decodes and validates Firebase ID token…
When was CVE-2026-13447 disclosed?
CVE-2026-13447 was first published on September 5, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13447 actively exploited?
CVE-2026-13447 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13447?
CVE-2026-13447 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-13447?
No fix for CVE-2026-13447 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-13447 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-13447?

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