How severe is CVE-2020-13942?

CVE-2020-13942 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-13942?

CVE-2020-13942 affects the following packages: org.apache.unomi:unomi (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-13942?

Update org.apache.unomi:unomi to 1.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13942 is resolved across your whole dependency graph.

How do I detect CVE-2020-13942 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.unomi:unomi. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2020-13942 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2020-13942?

O3 pinpoints whether CVE-2020-13942 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2020-13942 actively exploited in the wild?

Yes. There are 13 known exploit references for CVE-2020-13942, including 8 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2020-13942?

CVE-2020-13942 is classified as Improper Input Validation (CWE-20), CWE-74 (CWE-74). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2020-13942?

A Nuclei detection template exists for CVE-2020-13942, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-13942 published, and has it been updated?

CVE-2020-13942 was published on November 24, 2020 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2020-13942

CRITICAL

Injection and Improper Input Validation in Apache Unomi

Also known asGHSA-xp5j-wj4h-2jq9

Published

Nov 24, 2020

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

13 known

Blast Radius

1 pkg affected

☕org.apache.unomi:unomi

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.unomi:unomi`	all versions	1.5.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.