CVE-2026-62072

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-06. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

Update the WordPress Progress Planner plugin to the latest available version (at least 1.10.1) (from the CVE record's solution, Patchstack) — apply it.

Subscriber Broken Access Control in Progress Planner <= 1.10.0 versions.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Update the WordPress Progress Planner plugin to the latest available version (at least 1.10.1) (from the CVE record's solution, Patchstack). Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

Update the WordPress Progress Planner plugin to the latest available version (at least 1.10.1) (from the CVE record's solution, Patchstack). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 6, 2026

Advisory Details (1)

Auto-updated Oct 6, 2026
Fix named in the CVE record's solution (Patchstack).
Web page

Broken Access Control in WordPress Progress Planner Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/progress-planner/vulnerability/wordpress-progress-planner-plugin-1-10-0-broken-access-control-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-62072(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 33× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-11 19:34 UTCEG score recompute
  2. 2026-10-11 16:49 UTCEG score recompute
  3. 2026-10-11 15:14 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-10-11 14:11 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-11 03:16 UTCEG score recompute
  7. 2026-10-11 03:15 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-10-10 15:15 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-10 03:17 UTCEG score recompute
  11. 2026-10-10 03:17 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-09 15:17 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-09 03:17 UTCEG score recompute
  15. 2026-10-09 03:17 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-08 15:18 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-08 03:13 UTCEG score recompute
  19. 2026-10-08 03:13 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-07 15:15 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-07 03:17 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-10-06 15:19 UTCEG score recompute
  24. 2026-10-06 15:18 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Show 8 more
  1. 2026-10-06 11:28 UTCEG score recompute
  2. 2026-10-06 11:28 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-10-06 10:45 UTCEG score recompute
  4. 2026-10-06 10:45 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-10-06 09:57 UTCEG score recompute
  6. 2026-10-06 09:57 UTCGHSA enrichmentGHSA-mqg4-m7j5-x92p · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-06 08:52 UTCEG score recomputeFirst assessed: 8.8 HIGH
  8. 2026-10-06 08:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62072?
CVE-2026-62072 is a high-severity vulnerability; its CVE record was published on October 6, 2026. Subscriber Broken Access Control in Progress Planner <= 1.10.0 versions.
When was the CVE record for CVE-2026-62072 published?
The CVE record for CVE-2026-62072 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-62072 actively exploited?
CVE-2026-62072 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62072?
CVE-2026-62072 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62072?
The CVE record's solution for CVE-2026-62072, written by its CNA Patchstack, names the fix: "Update the WordPress Progress Planner plugin to the latest available version (at least 1.10.1)." The vendor advisories EchelonGraph has for CVE-2026-62072 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62072?

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

Book a Demo →Browse All CVEs