How severe is CVE-2019-0230?

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

Which packages are affected by CVE-2019-0230?

CVE-2019-0230 affects the following packages: org.apache.struts:struts2-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-0230?

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

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

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

How do I mitigate CVE-2019-0230 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-0230 actively exploited in the wild?

Yes. There are 12 known exploit references for CVE-2019-0230, including 1 documented proof-of-concept exploit on Exploit-DB and 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 CVE-2019-0230?

CVE-2019-0230 has an EPSS (Exploit Prediction Scoring System) score of 96.9%, placing it in the 100th 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 CVE-2019-0230?

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

Is there exploit tooling available for CVE-2019-0230?

A Nuclei detection template exists for CVE-2019-0230, 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-2019-0230 published, and has it been updated?

CVE-2019-0230 was published on September 14, 2020 and was last updated on October 24, 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

CRITICAL severity

CVE-2019-0230 — struts2-core

CRITICAL

CVE-2019-0230 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in org.apache.struts:struts2-core. 12 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.struts:struts2-core — see the affected versions and patch details below.

Improperly Controlled Modification of Dynamically-Determined Object Attributes in Apache Struts

Also known asGHSA-wp4h-pvgw-5727

Published

Sep 14, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

12 known

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

EPSS Exploitation Probability

via FIRST.org ↗

96.9%probability of exploitation in next 30 days

Very High Risk-0.45%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2019-0230 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕org.apache.struts:struts2-core

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

Apache Struts 2.0.0 to 2.5.20 forced double OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.struts:struts2-core`	≥ 2.0.0&&< 2.5.22	2.5.22`org.apache.struts:struts2-core:2.5.22`

Affected Products

5 products · 6 configurations

Application

strutsapache

≥ 2.0.0 && ≤ 2.5.20

range

Application

communications policy managementoracle

1 version

12.5.0

Application

financial services data integration huboracle

2 versions

8.0.38.0.6

Application

financial services market risk measurement and managementoracle

1 version

8.0.6

Application

mysql enterprise monitororacle

≤ 8.0.23

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.

EDB-49068remotemultiple

Apache Struts 2.5.20 - Double OGNL evaluation

by West Shepherd · Nov 17, 2020

Exploit-DB Source

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.struts:struts2-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.struts:struts2-core to 2.5.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0230 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.

How to detect CVE-2019-0230

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2019-0230 -u https://target

Template: Apache Struts <=2.5.20 - Remote Code Execution
Severity: critical
Impact: Successful exploitation of this vulnerability allows an attacker to execute arbitrary code on the affected server.
Remediation: Upgrade Apache Struts to a version higher than 2.5.20 or apply the necessary patches provided by the vendor.

Template by ProjectDiscovery nuclei-templates (geeknik), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

Apache Struts 2.0.0 to 2.5.20 forced double OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.

O3 Security · Impact-Aware SCA

Is CVE-2019-0230 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

Weaponization

OpenSSF Scorecard

Package health score

struts

8.4/10

Maintained10/10

Dependency-Update-Tool10/10

Code-Review0/10

Branch-ProtectionN/A

Vulnerabilities8/10

Assessed Oct 24, 2026

Timeline

Disclosed

Sep 14, 2020

First exploit

Nov 17, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2019-0230

GHSA-wp4h-pvgw-5727

References

Advisorycwiki.apache.org Advisorynvd.nist.gov Fixoracle.com Fixoracle.com Fixoracle.com Reportlaunchpad.support.sap.com Weblists.apache.org Weblists.apache.org Weblists.apache.org Weblists.apache.org Packagegithub.com Evidencepacketstormsecurity.com Evidencepacketstormsecurity.com

Related vulnerabilities

This CVE is critical severity; 2 of 8 other CVEs affecting struts2-core are rated as high or higher (top: critical).

CVE-2025-68493CVE-2025-66675CVE-2025-64775CVE-2024-53677CVE-2023-50164CVE-2023-41835CVE-2023-34396CVE-2023-34149

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-0230 — struts2-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2019-0230

Frequently Asked Questions

Is CVE-2019-0230 in your dependencies?