CVE-2020-13942

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 68.4%, top 1% 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
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 68%
CISA-KEV: Not listedEPSS: 68%CVSS: 9.8Exploit: NoneExposed: 0

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

It is possible to inject malicious OGNL or MVEL scripts into the /context.json public endpoint. This was partially fixed in 1.5.1 but a new attack vector was found. In Apache Unomi version 1.5.2 scripts are now completely filtered from the input. It is highly recommended to upgrade to the latest available version of the 1.5.x release to fix this problem.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
76(Track*)
EG Risk 76/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
Severity98% × 45%
Exploitation68% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.3%
KEV
Not listed

Published

November 24, 2020

Last Modified

November 21, 2024

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.unomi:unomi1.0.0-incubating ... 1.5.1 (6 versions)1.5.2

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 37× 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 01:49 UTCEG score recompute
  2. 2026-07-22 22:34 UTCEG score recompute
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-19 14:28 UTCEPSS rescore
  8. 2026-07-19 14:28 UTCEPSS rescore
  9. 2026-07-16 16:59 UTCEPSS rescore
  10. 2026-07-16 16:59 UTCEPSS rescore
  11. 2026-07-15 16:55 UTCEPSS rescore
  12. 2026-07-13 22:27 UTCEPSS rescore
  13. 2026-07-13 06:10 UTCEPSS rescore
  14. 2026-07-13 06:10 UTCEPSS rescore
  15. 2026-07-12 22:38 UTCOSV refresh
  16. 2026-07-11 08:24 UTCEPSS rescore
  17. 2026-07-09 19:06 UTCEPSS rescore
  18. 2026-07-08 15:11 UTCEPSS rescore
  19. 2026-07-06 16:25 UTCEPSS rescore
  20. 2026-07-06 16:25 UTCEPSS rescore
  21. 2026-07-05 02:27 UTCEPSS rescore
  22. 2026-07-04 06:28 UTCEPSS rescore
  23. 2026-07-01 15:03 UTCEPSS rescore
  24. 2026-07-01 15:03 UTCEPSS rescore
  25. 2026-06-30 23:20 UTCEPSS rescore
Show 31 more
  1. 2026-06-30 23:20 UTCEPSS rescore
  2. 2026-06-28 14:05 UTCEPSS rescore
  3. 2026-06-28 04:54 UTCEPSS rescore
  4. 2026-06-28 04:54 UTCEPSS rescore
  5. 2026-06-27 03:06 UTCEPSS rescore
  6. 2026-06-25 13:47 UTCEPSS rescore
  7. 2026-06-25 13:47 UTCEPSS rescore
  8. 2026-06-24 14:03 UTCEPSS rescore
  9. 2026-06-24 14:03 UTCEPSS rescore
  10. 2026-06-24 08:29 UTCOSV refresh
  11. 2026-06-23 21:31 UTCEPSS rescore
  12. 2026-06-23 21:31 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-21 01:57 UTCEPSS rescore
  15. 2026-06-19 19:23 UTCEPSS rescore
  16. 2026-06-19 19:23 UTCEPSS rescore
  17. 2026-06-18 17:50 UTCEPSS rescore
  18. 2026-06-18 17:50 UTCEPSS rescore
  19. 2026-06-17 17:50 UTCEPSS rescore
  20. 2026-06-17 17:50 UTCEPSS rescore
  21. 2026-06-15 17:46 UTCEPSS rescore
  22. 2026-06-13 22:58 UTCEPSS rescore
  23. 2026-06-13 22:58 UTCEPSS rescore
  24. 2026-06-07 12:29 UTCOSV refresh
  25. 2026-05-31 22:29 UTCEPSS rescore
  26. 2026-05-31 22:29 UTCEPSS rescore
  27. 2026-05-29 13:42 UTCEPSS rescore
  28. 2026-05-29 13:42 UTCEPSS rescore
  29. 2026-05-28 13:43 UTCEPSS rescore
  30. 2026-05-28 13:43 UTCEPSS rescore
  31. 2026-05-23 04:54 UTCEG score recompute

Publicly available exploits

(6 references)

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

  • GitHub PoCyaunsky/Unomi-CVE-2020-13942
    First seen Dec 22, 2020

    CVE-2020-13942 Apache Unomi 远程代码执行漏洞脚getshell

    Open source ↗
  • GitHub PoCblackmarketer/CVE-2020-13942
    First seen Nov 21, 2020
    Open source ↗
  • GitHub PoCshifa123/CVE-2020-13942-POC-
    First seen Nov 20, 2020

    CVE-2020-13942 POC + Automation Script

    Open source ↗
  • GitHub PoCeugenebmx/CVE-2020-13942
    First seen Nov 19, 2020

    CVE-2020-13942 unauthenticated RCE POC through MVEL and OGNL injection

    Open source ↗
  • GitHub PoClp008/CVE-2020-13942
    First seen Nov 18, 2020
    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-13942.yaml
    First seen Jan 1, 2020

    Apache Unomi <1.5.2 - Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2020-13942?
CVE-2020-13942 is a critical vulnerability published on November 24, 2020. It is possible to inject malicious OGNL or MVEL scripts into the /context.json public endpoint. This was partially fixed in 1.5.1 but a new attack vector was found. In Apache Unomi version 1.5.2 scripts are now completely filtered from the input. It is highly recommended to upgrade to the latest…
When was CVE-2020-13942 disclosed?
CVE-2020-13942 was first published in the National Vulnerability Database on November 24, 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-13942 actively exploited?
CVE-2020-13942 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-13942?
CVE-2020-13942 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2020-13942?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-13942, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-13942

Explore →

Is Your Infrastructure Affected by CVE-2020-13942?

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