What is CVE-2010-2273?

CVE-2010-2273 is a medium-severity cross-site scripting (XSS) vulnerability in dojo (npm), affecting versions = 1.13.0. It is fixed in 1.13.1, 1.12.4, 1.11.6, 1.10.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of dojo are affected by CVE-2010-2273?

dojo (npm) versions = 1.13.0 is affected.

Is there a fix for CVE-2010-2273?

Yes. CVE-2010-2273 is fixed in 1.13.1, 1.12.4, 1.11.6, 1.10.10. Upgrade to this version or later.

Is CVE-2010-2273 exploitable, and should I be worried?

Whether CVE-2010-2273 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-2010-2273 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-2010-2273?

Upgrade: dojo to 1.13.1 or later, dojo to 1.12.4 or later, dojo to 1.11.6 or later, dojo to 1.10.10 or later.

CVE-2010-2273 in dojo

Summary

Cross-Site Scripting in dojo

Versions of dojo prior to 1.4.2 are vulnerable to DOM-based Cross-Site Scripting (XSS). The package does not sanitize URL parameters in the _testCommon.js and runner.html test files, allowing attackers to execute arbitrary JavaScript in the victim's browser.

Impact

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.

Affected versions

dojo (= 1.13.0) dojo (>= 1.12.0, < 1.12.4) dojo (>= 1.11.0, < 1.11.6) dojo (>= 1.10.0, < 1.10.10)

Security releases

dojo → 1.13.1 (npm) dojo → 1.12.4 (npm) dojo → 1.11.6 (npm) dojo → 1.10.10 (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

Upgrade to version 1.4.2 or later.

Frequently Asked Questions

What is CVE-2010-2273? CVE-2010-2273 is a medium-severity cross-site scripting (XSS) vulnerability in dojo (npm), affecting versions = 1.13.0. It is fixed in 1.13.1, 1.12.4, 1.11.6, 1.10.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of dojo are affected by CVE-2010-2273? dojo (npm) versions = 1.13.0 is affected.
Is there a fix for CVE-2010-2273? Yes. CVE-2010-2273 is fixed in 1.13.1, 1.12.4, 1.11.6, 1.10.10. Upgrade to this version or later.
Is CVE-2010-2273 exploitable, and should I be worried? Whether CVE-2010-2273 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-2010-2273 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-2010-2273?
- Upgrade dojo to 1.13.1 or later
- Upgrade dojo to 1.12.4 or later
- Upgrade dojo to 1.11.6 or later
- Upgrade dojo to 1.10.10 or later

Other vulnerabilities in dojo

CVE-IDSeverityPackage summary

CVE-2021-23450Highdojo: Prototype Pollution in dojo CVE-2015-5654Mediumdojo: Cross-Site Scripting in dojo CVE-2008-6681Mediumdojo: Cross-Site Scripting in dojo CVE-2020-5258Highdojo: Prototype pollution in dojo