Is com.opensymphony:xwork 2.1 vulnerable?
Maven · 4 releases from 2.1.0 to 2.1.3 · latest com.opensymphony:xwork is 2.1.3 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. com.opensymphony:xwork 2.1.3, the last 2.1 release, is affected by 1 known security advisory (1 high), including CVE-2025-68493. 1 more affects earlier 2.1.x releases. At least one has no fixed release yet.
Is your project on an affected com.opensymphony:xwork?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting com.opensymphony:xwork 2.1.3
Apache Struts 2 is Missing XML Validation
- Affected
- >=2.0.0
- Fixed in
- No fix released
Fixed within 2.1.x, affecting earlier releases
Improper Input Validation in OpenSymphony XWork
- Affected
- <2.0.6 · >=2.1.0 <2.1.2
- Fixed in
- 2.0.6, 2.1.2
Every com.opensymphony:xwork 2.1.x release
Affected: 2.1.0 to 2.1.3.
| Version | Known advisories |
|---|---|
| com.opensymphony:xwork 2.1.3 | CVE-2025-68493 |
| com.opensymphony:xwork 2.1.2 | CVE-2025-68493 |
| com.opensymphony:xwork 2.1.1 | CVE-2025-68493, CVE-2008-6504 |
| com.opensymphony:xwork 2.1.0 | CVE-2025-68493, CVE-2008-6504 |
Which of your client projects are still on com.opensymphony:xwork 2.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact com.opensymphony:xwork version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other com.opensymphony:xwork versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.