CVE-2016-6795 json
Path Traversal in Apache Struts
published 2017-09-20 9 y ago modified 2026-06-17 4 mo ago also GHSA-44hv-jjx7-qfjg , EUVD-2022-2295
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.2%
- EPSS 8.2% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
In the Convention plugin in Apache Struts 2.3.x before 2.3.31, and 2.5.x before 2.5.5, it is possible to prepare a special URL which will be used for path traversal and execution of arbitrary code on server side.
Patch / fix
- maven org.apache.struts:struts2-convention-plugin 2.3.31, 2.5.5
Exploit prediction
8.22% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.struts:struts2-convention-plugin | >=2.3.0, <2.3.31 >=2.5.0, <2.5.5 |
2.3.31 2.5.5 |
Affected products
- Apache Software Foundation Apache Struts
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/apache/struts/commit/8e67b9144aa643769b261e2492cb561e04d016ab
web
-
github.com
/apache/struts/commit/c1869f4989942dd33fa4e189e0ac1f766fb5ac14
web
-
struts.apache.org
/docs/s2-042.html
web, vendor-advisory
-
securityfocus.com
/bid/93773
vdb-entry, third-party-advisory
- security.netapp.com /advisory/ntap-20180629-0003/
-
nvd.nist.gov
/vuln/detail/CVE-2016-6795
advisory
-
github.com
/apache/struts
package
-
security.netapp.com
/advisory/ntap-20180629-0003
web
-
web.archive.org
/web/20200227214705/http://www.securityfocus.com/bid/93773
web
Sources
- CVE List CVE-2016-6795
- GitHub Advisory GHSA-44hv-jjx7-qfjg
- NVD CVE-2016-6795
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.