What is CVE-2020-4051?

CVE-2020-4051 is a low-severity cross-site scripting (XSS) vulnerability in dijit (npm), affecting versions < 1.11.11. It is fixed in 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2020-4051?

CVE-2020-4051 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of dijit are affected by CVE-2020-4051?

dijit (npm) versions < 1.11.11 is affected.

Is there a fix for CVE-2020-4051?

Yes. CVE-2020-4051 is fixed in 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3. Upgrade to this version or later.

Is CVE-2020-4051 exploitable, and should I be worried?

Whether CVE-2020-4051 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-4051 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2020-4051?

Upgrade: dijit to 1.11.11 or later, dijit to 1.12.9 or later, dijit to 1.13.8 or later, dijit to 1.14.7 or later, dijit to 1.15.4 or later, dijit to 1.16.3 or later.

CVE-2020-4051 in dijit

Q: How severe is CVE-2020-4051?

CVE-2020-4051 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of dijit are affected by CVE-2020-4051?

dijit (npm) versions < 1.11.11 is affected.

Q: Is there a fix for CVE-2020-4051?

Yes. CVE-2020-4051 is fixed in 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3. Upgrade to this version or later.

Q: Is CVE-2020-4051 exploitable, and should I be worried?

Whether CVE-2020-4051 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-4051 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-4051?

Upgrade: dijit to 1.11.11 or later, dijit to 1.12.9 or later, dijit to 1.13.8 or later, dijit to 1.14.7 or later, dijit to 1.15.4 or later, dijit to 1.16.3 or later.

Summary

Cross-site Scripting in dijit editor's LinkDialog plugin

Workarounds

Users may apply the patch made in these releases.

For more information

If you have any questions or comments about this advisory, open an issue in dojo/dijit

Impact

XSS possible for users of the Dijit Editor's LinkDialog plugin

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2020-4051 has a CVSS score of 3.7 (Low). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3); upgrading removes the vulnerable code path.

Affected versions

dijit (< 1.11.11) dijit (>= 1.12.0, < 1.12.9) dijit (>= 1.13.0, < 1.13.8) dijit (>= 1.14.0, < 1.14.7) dijit (>= 1.15.0, < 1.15.4) dijit (>= 1.16.0, < 1.16.3)

Security releases

dijit → 1.11.11 (npm) dijit → 1.12.9 (npm) dijit → 1.13.8 (npm) dijit → 1.14.7 (npm) dijit → 1.15.4 (npm) dijit → 1.16.3 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Yes, 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3

Frequently Asked Questions

What is CVE-2020-4051? CVE-2020-4051 is a low-severity cross-site scripting (XSS) vulnerability in dijit (npm), affecting versions < 1.11.11. It is fixed in 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2020-4051? CVE-2020-4051 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of dijit are affected by CVE-2020-4051? dijit (npm) versions < 1.11.11 is affected.
Is there a fix for CVE-2020-4051? Yes. CVE-2020-4051 is fixed in 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3. Upgrade to this version or later.
Is CVE-2020-4051 exploitable, and should I be worried? Whether CVE-2020-4051 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-4051 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-4051?
- Upgrade dijit to 1.11.11 or later
- Upgrade dijit to 1.12.9 or later
- Upgrade dijit to 1.13.8 or later
- Upgrade dijit to 1.14.7 or later
- Upgrade dijit to 1.15.4 or later
- Upgrade dijit to 1.16.3 or later

Other vulnerabilities in dijit

CVE-IDSeverityPackage summary

CVE-2018-6561Mediumdijit: dijit editor cross-site scripting vulnerability