CVE-2020-13580

HIGHNVD 7.88.7▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.7 because EPSS predicts 73% probability of exploitation within the next 30 days (top 0.6% of all CVEs). NVD baseline CVSS 7.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.7EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 73%
CISA-KEV: Not listedEPSS PROB: 73%CVSS: 7.8Exploit: Elevated riskExposed: 0

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

An exploitable heap-based buffer overflow vulnerability exists in the PlanMaker document parsing functionality of SoftMaker Office 2021’s PlanMaker application. A specially crafted document can cause the document parser to explicitly trust a length from a particular record type and use it to write a 16-bit null relative to a buffer allocated on the stack. Due to a lack of bounds-checking on this value, this can allow an attacker to write to memory outside of the buffer and controllably corrupt memory. This can allow an attacker to earn code execution under the context of the application. An attacker can entice the victim to open a document to trigger this vulnerability.

CVSS v3
7.8
EG Score
8.7(high)
EG Risk
73(Track)
EG Risk 73/100SSVC: Track

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
Severity87% × 45%
Exploitation73% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
73%
EPSS %ILE
99%
KEV
Not listed

Published

February 4, 2021

Last Modified

November 21, 2024

References (2)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 17× 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-08-19 17:00 UTCEPSS rescore
  2. 2026-08-17 13:43 UTCEPSS rescore
  3. 2026-08-16 14:52 UTCEPSS rescore
  4. 2026-08-16 02:11 UTCEPSS rescore
  5. 2026-08-15 01:26 UTCEPSS rescore
  6. 2026-08-12 13:47 UTCEPSS rescore
  7. 2026-08-06 13:43 UTCEPSS rescore
  8. 2026-08-02 02:23 UTCEPSS rescore
  9. 2026-07-30 16:24 UTCEPSS rescore
  10. 2026-07-28 15:32 UTCEPSS rescore
  11. 2026-07-26 14:51 UTCEPSS rescore
  12. 2026-07-24 14:14 UTCEPSS rescore
  13. 2026-07-23 14:15 UTCEPSS rescore
  14. 2026-07-23 14:15 UTCEPSS rescore
  15. 2026-07-23 01:49 UTCEG score recompute▲ 0.90
  16. 2026-07-22 22:34 UTCEG score recompute
  17. 2026-07-22 14:05 UTCEPSS rescore
  18. 2026-07-21 15:22 UTCEPSS rescore
  19. 2026-07-21 15:22 UTCEPSS rescore
  20. 2026-07-20 17:04 UTCEPSS rescore
  21. 2026-07-19 02:26 UTCEPSS rescore
  22. 2026-07-19 02:26 UTCEPSS rescore
  23. 2026-07-18 10:02 UTCEPSS rescore
  24. 2026-07-15 16:55 UTCEPSS rescore
  25. 2026-07-13 06:10 UTCEPSS rescore
Show 58 more
  1. 2026-07-13 06:10 UTCEPSS rescore
  2. 2026-07-11 08:24 UTCEPSS rescore
  3. 2026-07-09 19:06 UTCEPSS rescore
  4. 2026-07-04 06:28 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-07-01 15:03 UTCEPSS rescore
  7. 2026-06-28 04:54 UTCEPSS rescore
  8. 2026-06-28 04:54 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-24 14:03 UTCEPSS rescore
  12. 2026-06-24 14:03 UTCEPSS rescore
  13. 2026-06-23 21:31 UTCEPSS rescore
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-21 01:57 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-17 17:50 UTCEPSS rescore
  19. 2026-06-15 17:46 UTCEPSS rescore
  20. 2026-06-14 23:15 UTCEPSS rescore
  21. 2026-06-14 23:15 UTCEPSS rescore
  22. 2026-06-13 22:58 UTCEPSS rescore
  23. 2026-06-13 22:58 UTCEPSS rescore
  24. 2026-06-12 23:09 UTCEPSS rescore
  25. 2026-06-11 13:58 UTCEPSS rescore
  26. 2026-06-10 22:16 UTCEPSS rescore
  27. 2026-06-10 22:16 UTCEPSS rescore
  28. 2026-06-10 13:20 UTCEPSS rescore
  29. 2026-06-08 14:15 UTCEPSS rescore
  30. 2026-06-08 14:15 UTCEPSS rescore
  31. 2026-06-07 15:23 UTCEPSS rescore
  32. 2026-06-07 15:23 UTCEPSS rescore
  33. 2026-06-06 13:45 UTCEPSS rescore
  34. 2026-06-06 13:45 UTCEPSS rescore
  35. 2026-06-06 13:45 UTCEPSS rescore
  36. 2026-06-05 22:45 UTCEPSS rescore
  37. 2026-06-05 22:45 UTCEPSS rescore
  38. 2026-06-05 06:08 UTCEPSS rescore
  39. 2026-06-04 13:10 UTCEPSS rescore
  40. 2026-06-04 13:10 UTCEPSS rescore
  41. 2026-06-02 20:11 UTCEPSS rescore
  42. 2026-06-02 20:11 UTCEPSS rescore
  43. 2026-06-01 13:50 UTCEPSS rescore
  44. 2026-05-31 22:29 UTCEPSS rescore
  45. 2026-05-31 22:29 UTCEPSS rescore
  46. 2026-05-31 00:15 UTCEPSS rescore
  47. 2026-05-31 00:14 UTCEPSS rescore
  48. 2026-05-29 13:42 UTCEPSS rescore
  49. 2026-05-29 13:42 UTCEPSS rescore
  50. 2026-05-28 13:43 UTCEPSS rescore
  51. 2026-05-28 13:43 UTCEPSS rescore
  52. 2026-05-27 13:39 UTCEPSS rescore
  53. 2026-05-26 21:21 UTCEG score recompute
  54. 2026-05-26 21:21 UTCGHSA enrichment
  55. 2026-05-26 13:42 UTCEPSS rescore
  56. 2026-05-26 13:42 UTCEPSS rescore
  57. 2026-05-26 07:17 UTCEPSS rescore
  58. 2026-05-26 07:17 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-13580?
CVE-2020-13580 is a high vulnerability published on February 4, 2021. An exploitable heap-based buffer overflow vulnerability exists in the PlanMaker document parsing functionality of SoftMaker Office 2021’s PlanMaker application. A specially crafted document can cause the document parser to explicitly trust a length from a particular record type and use it to write…
When was CVE-2020-13580 disclosed?
CVE-2020-13580 was first published in the National Vulnerability Database on February 4, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-13580 actively exploited?
CVE-2020-13580 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73% probability of exploitation in the next 30 days, which ranks it in the top 0.6% of all scored CVEs.
What is the CVSS score of CVE-2020-13580?
CVE-2020-13580 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.7.
How do I remediate CVE-2020-13580?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-13580, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-13580

Explore →

Is Your Infrastructure Affected by CVE-2020-13580?

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

Start Free Scan →Browse All CVEs