GHSA-2j39-qcjm-428w
CRITICALApache Struts vulnerable to path traversal
Blast Radius
org.apache.struts:struts2-core☕org.apache.struts:struts2-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An attacker can manipulate file upload params to enable paths traversal and under some circumstances this can lead to uploading a malicious file which can be used to perform Remote Code Execution. Users are recommended to upgrade to versions Struts 2.5.33 or Struts 6.3.0.2 or greater to fix this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.struts:struts2-core | ≥ 2.0.0&&< 2.5.33 | 2.5.33 |
| ☕Maven | org.apache.struts:struts2-core | ≥ 6.0.0&&< 6.3.0.2 | 6.3.0.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
An attacker can manipulate file upload params to enable paths traversal …
An attacker can manipulate file upload params to enable paths traversal …
An attacker can manipulate file upload params to enable paths traversal …
An attacker can manipulate file upload params to enable paths traversal …
An attacker can manipulate file upload params to enable paths traversal …
An attacker can manipulate file upload params to enable paths traversal …
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.struts:struts2-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.struts:struts2-core to 2.5.33 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2j39-qcjm-428w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2j39-qcjm-428w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-2j39-qcjm-428w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2j39-qcjm-428w in your dependencies?
O3 detects GHSA-2j39-qcjm-428w across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.