VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.struts:struts2-struts1-plugin: vulnerability history, versions and safety

org.apache.struts:struts2-struts1-plugin is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 55 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.struts:struts2-struts1-plugin vulnerabilities

Vulert verdict on org.apache.struts:struts2-struts1-plugin 2.3.37 i

Updated on 23 Oct 2026

Careful: 2.3.37 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.3.37 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 2 packages i
  • Stars 1,370 i
  • OpenSSF scorecard 6/10 i
  • Last release 93 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.struts:struts2-struts1-plugin, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.3.37 30 Dec 2018 C1 Apache-2.0 No Details →
2.3.36 22 Sep 2018 C1 Apache-2.0 No Details →
2.3.35 24 Jul 2018 C1 Apache-2.0 No Details →
2.3.34 05 Sep 2017 C1 Apache-2.0 No Details →
2.3.33 07 Jul 2017 C1 Apache-2.0 No Details →
2.3.32 06 Mar 2017 C1 Apache-2.0 No Details →
2.3.31 05 Oct 2016 C1 Apache-2.0 No Details →
2.3.30 07 Jul 2016 C1 Apache-2.0 No Details →
2.3.29 14 Jun 2016 C1 Apache-2.0 No Details →
2.3.24.3 20 Apr 2016 C1 Apache-2.0 No Details →
2.3.20.3 20 Apr 2016 C1 Apache-2.0 No Details →
2.3.28.1 19 Apr 2016 C1 Apache-2.0 No Details →
2.3.28 18 Mar 2016 C1 Apache-2.0 No Details →
2.3.24.1 22 Sep 2015 C1 Apache-2.0 No Details →
2.3.20.1 06 May 2015 C1 Apache-2.0 No Details →
2.3.24 03 May 2015 C1 Apache-2.0 No Details →
2.3.20 21 Nov 2014 C1 Apache-2.0 No Details →
2.3.16.3 02 May 2014 C1 Apache-2.0 No Details →
2.3.16.2 24 Apr 2014 C1 Apache-2.0 No Details →
2.3.16.1 01 Mar 2014 C1 Apache-2.0 No Details →
2.3.16 30 Nov 2013 C1 Apache-2.0 No Details →
2.3.15.3 15 Oct 2013 C1 Apache-2.0 No Details →
2.3.15.2 18 Sep 2013 C1 Apache-2.0 No Details →
2.3.15.1 14 Jul 2013 C1 Apache-2.0 No Details →
2.3.15 14 Jun 2013 C1 Apache-2.0 No Details →
2.3.14.3 03 Jun 2013 C1 Apache-2.0 No Details →
2.3.14.2 24 May 2013 C1 Apache-2.0 No Details →
2.3.14.1 18 Apr 2013 C1 Apache-2.0 No Details →
2.3.14 28 Mar 2013 C1 Apache-2.0 No Details →
2.3.12 06 Mar 2013 C1 Apache-2.0 No Details →
2.3.8 17 Dec 2012 C1 Apache-2.0 No Details →
2.3.7 06 Nov 2012 C1 Apache-2.0 No Details →
2.3.4.1 03 Aug 2012 C1 Apache-2.0 No Details →
2.3.4 12 May 2012 C1 Apache-2.0 No Details →
2.3.3 16 Apr 2012 C1 Apache-2.0 No Details →
2.3.1.2 20 Jan 2012 C1 Apache-2.0 No Details →
2.3.1.1 25 Dec 2011 C1 Apache-2.0 No Details →
2.3.1 08 Dec 2011 C1 Apache-2.0 No Details →
2.2.3.1 05 Sep 2011 C1 Apache-2.0 No Details →
2.2.3 08 Apr 2011 C1 Apache-2.0 No Details →
2.2.1.1 14 Dec 2010 C1 Apache-2.0 No Details →
2.2.1 17 Jul 2010 C1 Apache-2.0 No Details →
2.1.8.1 11 Nov 2009 C1 Apache-2.0 No Details →
2.1.8 29 Sep 2009 C1 Apache-2.0 No Details →
2.1.6 13 Jan 2009 C1 Apache-2.0 No Details →
2.0.14 22 Nov 2008 C1 Apache-2.0 No Details →
2.0.12 20 Oct 2008 C1 Apache-2.0 No Details →
2.0.11.2 29 Jun 2008 C1 Apache-2.0 No Details →
2.1.2 25 May 2008 C1 Apache-2.0 No Details →
2.0.11.1 04 Mar 2008 C1 Apache-2.0 No Details →
2.0.11 23 Oct 2007 C1 Apache-2.0 No Details →
2.0.9 24 Jul 2007 C1 Apache-2.0 No Details →
2.0.8 11 Jun 2007 C1 Apache-2.0 No Details →
2.0.6 23 Feb 2007 C1 Apache-2.0 No Details →
2.0.5 10 Feb 2007 C1 Apache-2.0 No Details →

All 55 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.struts:struts2-struts1-plugin

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-9791: Code execution in Apache Struts 1 plugin 9.8 critical No fix published 13 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.struts:struts2-struts1-plugin

Is org.apache.struts:struts2-struts1-plugin safe to use?

Vulert records 1 vulnerabilities for org.apache.struts:struts2-struts1-plugin in Maven: 1 critical, 0 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is org.apache.struts:struts2-struts1-plugin's Vulert package health score?

Vulert scores org.apache.struts:struts2-struts1-plugin 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of org.apache.struts:struts2-struts1-plugin affected?

Yes. 2.3.37, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does org.apache.struts:struts2-struts1-plugin have?

1 vulnerability is recorded for org.apache.struts:struts2-struts1-plugin in the Maven ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.struts:struts2-struts1-plugin vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.struts:struts2-struts1-plugin in the last 12 months, and the oldest entry in this database dates to 13 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.struts:struts2-struts1-plugin are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.struts:struts2-struts1-plugin for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.struts:struts2-struts1-plugin version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.