How severe is CVE-2019-12416?

CVE-2019-12416 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-12416?

CVE-2019-12416 affects the following packages: org.apache.deltaspike:deltaspike (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-12416?

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

How do I detect CVE-2019-12416 in my Maven dependencies?

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

How do I mitigate CVE-2019-12416 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.

Is CVE-2019-12416 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2019-12416, including 1 in-the-wild exploitation 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 CVE-2019-12416?

CVE-2019-12416 has an EPSS (Exploit Prediction Scoring System) score of 2.7%, placing it in the 86th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-12416?

CVE-2019-12416 is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-12416 published, and has it been updated?

CVE-2019-12416 was published on March 19, 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

Not in CISA KEV

MEDIUM severity

CVE-2019-12416 — deltaspike

MEDIUM

CVE-2019-12416 is a medium-severity (CVSS 6.1) CWE-74 vulnerability in org.apache.deltaspike:deltaspike. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.apache.deltaspike:deltaspike — see the affected versions and patch details below.

Injection in DeltaSpike

Also known asGHSA-rhg5-fqr3-hrf5

Published

Mar 19, 2020

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-12416 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕org.apache.deltaspike:deltaspike

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

we got reports for 2 injection attacks against the DeltaSpike windowhandler.js. This is only active if a developer selected the ClientSideWindowStrategy which is not the default.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.deltaspike:deltaspike`	all versions	1.9.4`org.apache.deltaspike:deltaspike:1.9.4`

Affected Products

1 product · 1 configurations

Application

deltaspikeapache

≤ 1.9.2

range

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.

we got reports for 2 injection attacks against the DeltaSpike windowhand…

lists.apache.orgNVDSep 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.deltaspike:deltaspike, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.deltaspike:deltaspike to 1.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12416 is resolved across your whole dependency graph.
Workarounds
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.

Frequently Asked Questions

we got reports for 2 injection attacks against the DeltaSpike windowhandler.js. This is only active if a developer selected the ClientSideWindowStrategy which is not the default.

O3 Security · Impact-Aware SCA

Is CVE-2019-12416 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-74CWE-74

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Mar 19, 2020

First exploit

Sep 21, 2020

Last updated

Jul 8, 2026

Identifiers

CVE-2019-12416

GHSA-rhg5-fqr3-hrf5

References

Advisorynvd.nist.gov Weblists.apache.org Weblists.apache.org Evidencelists.apache.org

Related vulnerabilities

This CVE is medium severity; 6 of 8 other CVEs with CWE-74 are rated as high or higher (top: high).

GHSA-wwv5-g3v4-889xCVE-2026-55558GHSA-h58c-xccx-75m3CVE-2026-54543GHSA-c7hr-448w-65pxGHSA-jm78-9fvv-mhgrCVE-2026-71320CVE-2026-16729Browse all CWE-74

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026