CVE-2018-1000665 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.dojotoolkit:dojo. A fix is available for org.dojotoolkit:dojo — see the affected versions and patch details below.
Improper Neutralization of Input During Web Page Generation in Dojo Dojo Objective Harness
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.dojotoolkit:dojoReal-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
Dojo Dojo Objective Harness (DOH) version prior to version 1.14 contains a Cross Site Scripting (XSS) vulnerability in unit.html and testsDOH/_base/loader/i18n-exhaustive/i18n-test/unit.html and testsDOH/_base/i18nExhaustive.js in the DOH that can result in Victim attacked through their browser - deliver malware, steal HTTP cookies, bypass CORS trust. This attack appear to be exploitable via Victims are typically lured to a web site under the attacker's control; the XSS vulnerability on the target domain is silently exploited without the victim's knowledge. This vulnerability appears to have been fixed in 1.14.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.dojotoolkit:dojo | all versions | 1.14org.dojotoolkit:dojo:1.14 |
Affected Products
dojodojotoolkitDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.dojotoolkit:dojo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.dojotoolkit:dojo to 1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000665 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2018-1000665 in your dependencies?
Find it across Maven, including transitive dependencies.