How severe is GHSA-536q-8gxx-m782?

No CVSS score has been assigned to GHSA-536q-8gxx-m782 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-536q-8gxx-m782?

GHSA-536q-8gxx-m782 affects the following packages: dojo (npm), dojo (npm), dojo (npm), dojo (npm). Ecosystems affected: npm.

How do I fix GHSA-536q-8gxx-m782?

Update dojo to 1.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-536q-8gxx-m782 is resolved across your whole dependency graph.

How do I detect GHSA-536q-8gxx-m782 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dojo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-536q-8gxx-m782 if there is no patch (or I can't update yet)?

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.

Is GHSA-536q-8gxx-m782 actively exploited in the wild?

Yes. There are 3 known exploit references for GHSA-536q-8gxx-m782, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-536q-8gxx-m782?

GHSA-536q-8gxx-m782 has an EPSS (Exploit Prediction Scoring System) score of 4.5%, placing it in the 91th 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.

What type of vulnerability is GHSA-536q-8gxx-m782?

GHSA-536q-8gxx-m782 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-536q-8gxx-m782 published, and has it been updated?

GHSA-536q-8gxx-m782 was published on September 11, 2019 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Cross-Site Scripting in dojoGHSA-536q-8gxx-m782

Fix: dojo/dojo#307

GHSA-536q-8gxx-m782 is a Cross-site Scripting (XSS) vulnerability in dojo. 3 public exploit references exist, so weaponization risk is real. A fix is available for dojo — see the affected versions and patch details below.

Also known asCVE-2010-2273

Published

Sep 11, 2019

Updated

Nov 8, 2023

Affected

4 pkgs

Patched

4 / 4

Exploits

3 known

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

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

Real-World Exposure

4 pkgs affected

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.

31other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

dojonpm

15Kdownloads / week

Description

Multiple cross-site scripting (XSS) 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 inject arbitrary web script or HTML 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, and util/buildscripts/jslib/buildUtil.js, as demonstrated by the (1) dojoUrl and (2) testUrl parameters to util/doh/runner.html.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`dojo`	≥ 1.13.0&&< 1.13.1	1.13.1`npm install dojo@1.13.1`
📦npm	`dojo`	≥ 1.12.0&&< 1.12.4	1.12.4`npm install dojo@1.12.4`
📦npm	`dojo`	≥ 1.11.0&&< 1.11.6	1.11.6`npm install dojo@1.11.6`
📦npm	`dojo`	≥ 1.10.0&&< 1.10.10	1.10.10`npm install dojo@1.10.10`

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

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-33765webappsmultiple✓ Verified

Dojo Toolkit 1.4.1 - '/doh/runner.html' Multiple Cross-Site Scripting Vulnerabilities

by Adam Bixby · Mar 15, 2010

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dojo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dojo to 1.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-536q-8gxx-m782 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

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. ## Recommendation Upgrade to version 1.4.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-536q-8gxx-m782 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works