# Apache Struts's ParameterInterceptor component does not prevent access to public constructors

Advisory record · `GHSA-hxqq-w4mr-mc62`

- **Identifiers:** `GHSA-hxqq-w4mr-mc62` · `CVE-2012-0393`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Published:** 4 May 2022
- **Updated:** 3 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 May 2022, 00:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.struts:struts2-core` (Maven): affected `<2.3.1.1`; fixed in `2.3.1.1`
- `org.apache.struts.xwork:xwork-core` (Maven): affected `<2.2.3.1`; fixed in `2.2.3.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The ParameterInterceptor component in Apache Struts 2 (org.apache.struts:struts2-core before 2.3.1.1) and xwork-core (org.apache.struts.xwork:xwork-core before 2.2.3.1) does not prevent access to public constructors. A remote attacker can send a crafted request parameter that creates a Java object, allowing them to create or overwrite arbitrary files. Upgrade struts2-core to 2.3.1.1 or xwork-core to 2.2.3.1.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.36, the 98th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hxqq-w4mr-mc62)

## Sources

- [GitHub Advisory Database: GHSA-hxqq-w4mr-mc62](https://github.com/advisories/GHSA-hxqq-w4mr-mc62)
- [OSV: GHSA-hxqq-w4mr-mc62](https://osv.dev/vulnerability/GHSA-hxqq-w4mr-mc62)
- <https://nvd.nist.gov/vuln/detail/CVE-2012-0393>
- <https://github.com/apache/struts/commit/25e50069d60434a30395e3a98357ffba2bed427e>
- <https://github.com/apache/struts/commit/9cad25f258bb2629d263f828574d2671366c238d>
- <https://github.com/apache/struts>
- <https://web.archive.org/web/20120612142634/https://sec-consult.com/files/20120104-0_Apache_Struts2_Multiple_Critical_Vulnerabilities.txt>
- <https://web.archive.org/web/20140723153720/http://secunia.com/advisories/47393>
- <http://archives.neohapsis.com/archives/bugtraq/2012-01/0031.html>
- <http://struts.apache.org/2.x/docs/s2-008.html>
- <http://struts.apache.org/2.x/docs/version-notes-2311.html>
- <http://www.exploit-db.com/exploits/18329>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hxqq-w4mr-mc62>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hxqq-w4mr-mc62/>. Everything for agents: <https://agentprime.io/llms.txt>.
