CVE-2020-4463

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 31.6%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 32%CVSS: 8.2Exploit: NoneExposed: 0

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

IBM Maximo Asset Management 7.6.0.1 and 7.6.0.2 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 181484.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
57(Track)
EG Risk 57/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
Severity82% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.1%
KEV
Not listed

Published

July 29, 2020

Last Modified

November 21, 2024

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCIbonok/CVE-2020-4463
    First seen Aug 13, 2020

    IBM Maximo Asset Management is vulnerable to Information Disclosure via XXE Vulnerability (CVE-2020-4463)

    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-4463.yaml
    First seen Jan 1, 2020

    IBM Maximo Asset Management Information Disclosure - XML External Entity Injection

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-4463?
CVE-2020-4463 is a high vulnerability published on July 29, 2020. IBM Maximo Asset Management 7.6.0.1 and 7.6.0.2 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 181484.
When was CVE-2020-4463 disclosed?
CVE-2020-4463 was first published in the National Vulnerability Database on July 29, 2020, 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-4463 actively exploited?
CVE-2020-4463 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-4463?
CVE-2020-4463 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2020-4463?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-4463, 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-4463

Explore →

Is Your Infrastructure Affected by CVE-2020-4463?

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

Start Free Scan →Browse All CVEs