dbcve.org
StrutsFramework / library · Apache

CVE-2015-2992

MEDIUM · 6.1 CVSS v3.1 Published 2020-02-27
Fix available
A fix is available. Upgrade to 2.3.20 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Apache Struts before 2.3.20 has a cross-site scripting (XSS) vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Apache Struts versions prior to 2.3.20 contain a cross-site scripting (XSS) vulnerability, allowing attackers to inject malicious scripts into web pages viewed by other users.

MitigationUpgrade Apache Struts to version 2.3.20 or later to resolve the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StrutsFramework / library
Affected:>= 2.0.0, < 2.3.20

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Apache Struts library version
    Check the Struts JAR file name in your application's lib directory, or inspect the manifest file (META-INF/MANIFEST.MF) within the struts2-core JAR. The version is typically listed in the Implementation-Version or Bundle-Version field.
    Affected if The version shown is 2.0.0 or higher but lower than 2.3.20
  2. Verify Struts version in application dependencies
    If using a build tool (Maven, Gradle), review your pom.xml or build.gradle file for the struts2-core dependency version. Alternatively, check the lib/struts2-core.jar file naming convention which often includes the version number.
    Affected if The declared dependency version falls within the range 2.0.0 to 2.3.19 inclusive
  3. Confirm Struts is actively serving web requests
    Review your web application configuration (web.xml) to ensure the StrutsPrepareAndExecuteFilter or equivalent Struts filter is mapped and active. Check that your application server (Tomcat, Jetty, etc) is running and the Struts-based application is deployed and accessible.
    Affected if The Struts filter is configured and the application is running, meaning user-supplied input could be processed through vulnerable Struts components

You are affected if your deployed Apache Struts version is 2.0.0 or higher but below 2.3.20 and your application is actively processing web requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2.3.20 or later
Fixed in 2.3.20
Interim mitigation

Upgrade Apache Struts to version 2.3.20 or later to resolve the vulnerability.

Fix this in Struts Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-2992 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data