GHSA-536q-8gxx-m782
Fix: dojo/dojo#307GHSA-536q-8gxx-m782 is a Cross-site Scripting (XSS) vulnerability in dojo. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-536q-8gxx-m782 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Cross-Site Scripting in dojo
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
dojonpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | dojo | ≥ 1.13.0&&< 1.13.1 | 1.13.1 |
| 📦npm | dojo | ≥ 1.12.0&&< 1.12.4 | 1.12.4 |
| 📦npm | dojo | ≥ 1.11.0&&< 1.11.6 | 1.11.6 |
| 📦npm | dojo | ≥ 1.10.0&&< 1.10.10 | 1.10.10 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Dojo Toolkit 1.4.1 - '/doh/runner.html' Multiple Cross-Site Scripting Vulnerabilities
by Adam Bixby · Mar 15, 2010
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dojo. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-536q-8gxx-m782 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-536q-8gxx-m782. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-536q-8gxx-m782 in your dependencies?
O3 detects GHSA-536q-8gxx-m782 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.