CVE-2007-6726 json
Apache Struts Dojo Plugin XSS Vulnerability
published 17y ago modified 4mo ago also GHSA-rm26-w253-9qv7 , EUVD-2022-5192
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.4%
- EPSS 3.4% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
Multiple cross-site scripting (XSS) vulnerabilities in Dojo 0.4.1 and 0.4.2, as used in Apache Struts and other products, allow remote attackers to inject arbitrary web script or HTML via unspecified vectors involving (1) xip_client.html and (2) xip_server.html in src/io/.
Patch / fix
- maven org.apache.struts:struts2-dojo-plugin 0.4.3
Is CVE-2007-6726 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.45% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-16).
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:struts2-dojo-plugin | >=0.4.1, <0.4.3 |
0.4.3 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
dojotoolkit.org
/releaseNotes/0.4.3
web, patch, vendor-advisory
-
dojotoolkit.org
/2007/05/26/0-4-3-released-0-4-2-and-0-4-1-users-should-upgrade-immediately
web, patch, vendor-advisory
-
dojotoolkit.org
/0-4-3-and-updated-0-4-1-0-4-2-builds
web, patch, vendor-advisory
-
issues.apache.org
/struts/browse/WW-2134
web, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49884
vdb-entry, web
-
securityfocus.com
/bid/34660
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2007-6726
advisory
-
github.com
/apache/struts-archive/blob/master/plugins/struts2-dojo-plugin
web
Sources
- CVE List CVE-2007-6726
- GitHub Advisory GHSA-rm26-w253-9qv7
- NVD CVE-2007-6726
Fencer Intel 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.