CVE-2013-2115
highpriority · attend · 68EPSS 0.746 · 99 %ileexploit · weaponizedEURUUSEPSS · scored 2026-10-27
Apache Struts 2 before 2.3.14.2 allows remote attackers to execute arbitrary OGNL code via a crafted request that is not properly handled when using the includeParams attribute in the (1) URL or (2) A tag. NOTE: this issue is due to an incomplete fix for CVE-2013-1966.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (2)
Public proof-of-concept and weaponised exploit code.
- exploit/multi/http/struts_include_paramsApache Struts includeParams Remote Code Executionweaponized · metasploit
- EDB-25980Apache Struts - includeParams Remote Code Execution (Metasploit)functional · exploit_db
affected products (7)
Products and version ranges known to be affected.
- Maven org.apache.struts.xwork:xwork-core2.0.0 → 2.3.14.2osvUSpkg:maven/org.apache.struts.xwork/xwork-core
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-7ghm-rpc7-p7g5Code injection in Apache Struts2022-05-13ghsa · osvUS
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 an OGNL expression to enable method execution and execute arbitrary methods, bypassing Struts and OGNL library protections. The issue was originally addressed by Struts 2.3.14.1 and Security Announcement [S2-013](https://cwiki.apache.org/confluence/display/WW/S2-013). However, the solution introduced with 2.3.14.1 did not address all possible attack vectors, such that every version of Struts 2 before 2.3.14.2 is still vulnerable to such attacks.
also known as (4)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (12)
External citations — patches, advisories, analysis.
- http://struts.apache.org/development/2.x/docs/s2-014.htmlcnnvd
- https://bugzilla.redhat.com/show_bug.cgi?id=967656cnnvd
- https://cwiki.apache.org/confluence/display/WW/S2-014cnnvd
- https://www.securityfocus.com/bid/60167cnnvd
- http://struts.apache.org/development/2.x/docs/s2-014.htmlenisa_euvd
- http://www.securityfocus.com/bid/60167enisa_euvd
- https://bugzilla.redhat.com/show_bug.cgi?id=967656enisa_euvd
- https://cwiki.apache.org/confluence/display/WW/S2-014enisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan