Cross-Site Request Forgery in Apache Struts
Published 17 May 2022 · Updated 7 Dec 2024
Is your project on an affected org.apache.struts:struts2-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=2.0.0 <2.3.4.1
- Fixed in
- 2.3.4.1
mvn versions:use-dep-version -Dincludes=org.apache.struts:struts2-core -DdepVersion=2.3.4.1 -DforceVersion=trueDetails
The token check mechanism in Apache Struts 2.0.0 through 2.3.4 does not properly validate the token name configuration parameter, which allows remote attackers to perform cross-site request forgery (CSRF) attacks by setting the token name configuration parameter to a session attribute.
Is GHSA-2rvh-q539-q33v in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.struts:struts2-core, and gives you the command that fixes it.
More advisories for org.apache.struts:struts2-core
- HighCVE-2025-68493Apache Struts 2 is Missing XML Validation · 11 Jan 2026
- HighCVE-2025-66675Apache Struts has a Denial of Service vulnerability · 10 Dec 2025
- HighCVE-2025-64775Apache Struts is Vulnerable to DoS via File Leak · 1 Dec 2025
- CriticalCVE-2024-53677Apache Struts file upload logic is flawed · 11 Dec 2024
- CriticalCVE-2023-50164Apache Struts vulnerable to path traversal · 7 Dec 2023
- HighCVE-2023-41835Apache Struts Improper Control of Dynamically-Managed Code Resources vulnerability · 5 Dec 2023
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.