How severe is CVE-2010-2274?

No CVSS score has been assigned to CVE-2010-2274 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-2274?

CVE-2010-2274 affects the following packages: org.dojotoolkit:dojo (Maven), org.dojotoolkit:dojo (Maven), org.dojotoolkit:dojo (Maven), org.dojotoolkit:dojo (Maven), org.dojotoolkit:dojo (Maven). Ecosystems affected: Maven.

How do I fix CVE-2010-2274?

Update org.dojotoolkit:dojo to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-2274 is resolved across your whole dependency graph.

How do I detect CVE-2010-2274 in my Maven dependencies?

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.

How do I mitigate CVE-2010-2274 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2010-2274 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-2274 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2010-2274?

CVE-2010-2274 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 80th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2010-2274 published, and has it been updated?

CVE-2010-2274 was published on June 15, 2010 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2010-2274: dojo Open Redirect

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

☕org.dojotoolkit:dojo☕org.dojotoolkit:dojo☕org.dojotoolkit:dojo☕org.dojotoolkit:dojo☕org.dojotoolkit:dojo

Real-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

Multiple open redirect vulnerabilities in Dojo 1.0.x before 1.0.3, 1.1.x before 1.1.2, 1.2.x before 1.2.4, 1.3.x before 1.3.3, and 1.4.x before 1.4.2 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors, possibly related to dojo/resources/iframe_history.html, dojox/av/FLAudio.js, dojox/av/FLVideo.js, dojox/av/resources/audio.swf, dojox/av/resources/video.swf, util/buildscripts/jslib/build.js, util/buildscripts/jslib/buildUtil.js, and util/doh/runner.html.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.dojotoolkit:dojo`	≥ 1.0.0&&< 1.0.3	1.0.3`org.dojotoolkit:dojo:1.0.3`
☕Maven	`org.dojotoolkit:dojo`	≥ 1.1.0&&< 1.1.2	1.1.2`org.dojotoolkit:dojo:1.1.2`
☕Maven	`org.dojotoolkit:dojo`	≥ 1.2.0&&< 1.2.4	1.2.4`org.dojotoolkit:dojo:1.2.4`
☕Maven	`org.dojotoolkit:dojo`	≥ 1.3.0&&< 1.3.3	1.3.3`org.dojotoolkit:dojo:1.3.3`
☕Maven	`org.dojotoolkit:dojo`	≥ 1.4.0&&< 1.4.2	1.4.2`org.dojotoolkit:dojo:1.4.2`

Affected Products

1 product · 14 configurations

Application

dojodojotoolkit

14 versions

1.01.0.11.0.21.11.1.11.21.2.11.2.21.2.31.31.3.11.3.2

Detection & mitigation playbook

Open-source dependency

Detect
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.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-2274 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

Multiple open redirect vulnerabilities in Dojo 1.0.x before 1.0.3, 1.1.x before 1.1.2, 1.2.x before 1.2.4, 1.3.x before 1.3.3, and 1.4.x before 1.4.2 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors, possibly related to dojo/resources/iframe_history.html, dojox/av/FLAudio.js, dojox/av/FLVideo.js, dojox/av/resources/audio.swf, dojox/av/resources/video.swf, util/buildscripts/jslib/build.js, util/buildscripts/jslib/buildUtil.js, and util/doh/runner.html.

O3 Security · Impact-Aware SCA

Is CVE-2010-2274 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2010-2274 — dojo