Skip to content

Product

org.apache.struts/struts2-core vulnerabilities

63 published CVES affecting org.apache.struts/struts2-core, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
63
Critical
15
High
26
Medium
21
Low
1
Unscored
0
CISA KEV
6

Latest org.apache.struts/struts2-core CVEs

Newest publication first · page 1 of 3

  1. CriticalCVSS 9.8 EPSS 1.7%

    Improper neutralization of special elements used in an expression language statement ('Expression Language Injection') vulnerability in Apache Struts. If the application is configured to use the legacy RESTful action mapper, a crafted request can inject an OGNL expression that ma...

  2. HighCVSS 7.5 EPSS 7.3%

    When a Multipart request is performed but some of the fields exceed the maxStringLength limit, the upload files will remain in struts.multipart.saveDir even if the request has been denied. Users are recommended to upgrade to versions Struts 2.5.32 or 6.1.2.2 or Struts 6.3.0.1 or...

  3. CriticalCVSS 9.8 EPSS 96.3% CISA KEV added 2021-11-03 Exploited in the wild Framework module Public exploit PoC

    Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution. Affected software : Apache Struts 2.0.0 - Struts 2.5.25.

  4. HighCVSS 8.1 EPSS 100.0% CISA KEV added 2021-11-03 Exploited in the wild Framework module Public exploit PoC

    Apache Struts versions 2.3 to 2.3.34 and 2.5 to 2.5.16 suffer from possible Remote Code Execution when alwaysSelectFullNamespace is true (either by user or a plugin like Convention Plugin) and then: results are used with no namespace and in same time, its upper package have no or...

  5. HighCVSS 8.8 EPSS 8.1%

    Apache Struts 2.x before 2.3.29 allows remote attackers to execute arbitrary code via a "%{}" sequence in a tag attribute, aka forced double OGNL evaluation. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-0785.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.