Skip to content

← Actionable
High, CVSS 8.1

Code injection in Apache Struts

CVE-2013-2115GHSA-7ghm-rpc7-p7g5

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.apache.struts.xwork:xwork-core 2.3.14.2; org.apache.struts:struts2-core 2.3.14.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2013-2115: 74.64% estimated exploitation activity in the next 30 days; percentile 99.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A vulnerability introduced by forcing parameter inclusion in the URL and Anchor Tag allows remote command execution, session access and manipulation and XSS attacks. both the s:url and s:a tag provide an includeParams attribute. The main scope of that attribute is to understand whether includes http request parameter or not. The allowed values of includeParams are: none - include no parameters in the URL (default) get - include only GET parameters in the URL all - include both GET and POST parameters in the URL A request that included a specially crafted request parameter could be used to inject arbitrary OGNL code into the stack, afterward used as request parameter of an URL or A tag , which will cause a further evaluation. The second evaluation happens when the URL/A tag tries to resolve every parameters present in the original request. This lets malicious users put arbitrary OGNL statements into any request parameter (not necessarily managed by the code) and have it evaluated as…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-7ghm-rpc7-p7g5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-2115

Advisory: Code injection in Apache Struts
IDs: CVE-2013-2115, GHSA-7ghm-rpc7-p7g5
Record: https://patchnext.com/advisories/cve-2013-2115 (revision 1, source checked 26 Oct 2026, 16:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.struts.xwork:xwork-core 2.3.14.2; org.apache.struts:struts2-core 2.3.14.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.struts.xwork:xwork-core: affected >= 2.0.0, < 2.3.14.2; fixed in 2.3.14.2
- Maven org.apache.struts:struts2-core: affected >= 2.0.0, < 2.3.14.2; fixed in 2.3.14.2

## Suggested inspection (read-only)
- Maven org.apache.struts.xwork:xwork-core: check the installed version with your package manager.
- Maven org.apache.struts:struts2-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.struts.xwork:xwork-core, org.apache.struts:struts2-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7ghm-rpc7-p7g5 (GitHub-reviewed advisory GHSA-7ghm-rpc7-p7g5 lists affected ranges: Maven org.apache.struts:struts2-core >=2.0.0 =2.0.0 <2.3.14.2)

Commands are suggestions: review each one before running it.

Loading voting…