Skip to content
Fencer Vulns
medium 4.3

CVE-2005-3745 json

Apache Struts Cross-site scripting Vulnerability

published 2005-11-22 20 y ago modified 2026-06-16 4 mo ago also GHSA-9cjh-qmvx-436c , EUVD-2022-3353

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
25.7%
EPSS 25.7% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

Cross-site scripting (XSS) vulnerability in Apache Struts 1.2.7, and possibly other versions allows remote attackers to inject arbitrary web script or HTML via the query string, which is not properly quoted or filtered when the request handler generates an error message.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2005-3745 updated

security flaw

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-26542)
  2. Published

Exploit prediction

25.71% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-26542 Apache Struts 1.2.7 - Error Response Cross-Site Scripting remote, 2005-11-21
  • securityfocus.com http://www.securityfocus.com/bid/15512 referenced PoC, tagged "exploit" by a source, unverified
  • hacktics.com http://www.hacktics.com/AdvStrutsNov05.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.struts:struts-core
<=1.2.7
 no fix listed

Classification

Weakness
  • CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page

References

Sources

Fencer Vulns 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.