CVE-2020-4051 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in dijit. A fix is available for dijit — see the affected versions and patch details below.
Cross-site Scripting in dijit editor's LinkDialog plugin
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
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
dijitnpmDescription
In Dijit before versions 1.11.11, and greater than or equal to 1.12.0 and less than 1.12.9, and greater than or equal to 1.13.0 and less than 1.13.8, and greater than or equal to 1.14.0 and less than 1.14.7, and greater than or equal to 1.15.0 and less than 1.15.4, and greater than or equal to 1.16.0 and less than 1.16.3, there is a cross-site scripting vulnerability in the Editor's LinkDialog plugin. This has been fixed in 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | dijit | all versions | 1.11.11npm install dijit@1.11.11 |
| 📦npm | dijit | ≥ 1.12.0&&< 1.12.9 | 1.12.9npm install dijit@1.12.9 |
| 📦npm | dijit | ≥ 1.13.0&&< 1.13.8 | 1.13.8npm install dijit@1.13.8 |
| 📦npm | dijit | ≥ 1.14.0&&< 1.14.7 | 1.14.7npm install dijit@1.14.7 |
| 📦npm | dijit | ≥ 1.15.0&&< 1.15.4 | 1.15.4npm install dijit@1.15.4 |
| 📦npm | dijit | ≥ 1.16.0&&< 1.16.3 | 1.16.3npm install dijit@1.16.3 |
Affected Products
debian linuxdebianactive iq unified managernetapponcommand insightnetapponcommand workflow automationnetappsnapcenternetappdijitopenjsfDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dijit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dijit to 1.11.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-4051 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-2020-4051 in your dependencies?
Find it across npm, including transitive dependencies.