How severe is GHSA-xp5j-wj4h-2jq9?

GHSA-xp5j-wj4h-2jq9 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xp5j-wj4h-2jq9?

GHSA-xp5j-wj4h-2jq9 affects the following packages: org.apache.unomi:unomi (Maven). Ecosystems affected: Maven.

How do I fix GHSA-xp5j-wj4h-2jq9?

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 GHSA-xp5j-wj4h-2jq9 is resolved across your whole dependency graph.

How do I detect GHSA-xp5j-wj4h-2jq9 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.unomi:unomi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xp5j-wj4h-2jq9 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 GHSA-xp5j-wj4h-2jq9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xp5j-wj4h-2jq9 can be triaged on real exposure rather than presence alone.

Is GHSA-xp5j-wj4h-2jq9 actively exploited in the wild?

Yes. There are 13 known exploit references for GHSA-xp5j-wj4h-2jq9, 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 is the EPSS score for GHSA-xp5j-wj4h-2jq9?

GHSA-xp5j-wj4h-2jq9 has an EPSS (Exploit Prediction Scoring System) score of 68.4%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-xp5j-wj4h-2jq9?

GHSA-xp5j-wj4h-2jq9 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 GHSA-xp5j-wj4h-2jq9?

A Nuclei detection template exists for GHSA-xp5j-wj4h-2jq9, 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 GHSA-xp5j-wj4h-2jq9 published, and has it been updated?

GHSA-xp5j-wj4h-2jq9 was published on February 10, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

GHSA-xp5j-wj4h-2jq9 — unomi

CRITICAL

GHSA-xp5j-wj4h-2jq9 is a critical-severity (CVSS 9.8) Improper Input Validation vulnerability in org.apache.unomi:unomi. 13 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.unomi:unomi — see the affected versions and patch details below.

Injection and Improper Input Validation in Apache Unomi

Also known asCVE-2020-13942

Published

Feb 10, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

13 known

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

68.4%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-xp5j-wj4h-2jq9 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

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`org.apache.unomi:unomi: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.