GHSA-pg97-ww7h-5mjr is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in dojox. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-pg97-ww7h-5mjr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
XSS in dojox due to insufficient escape in dojox.xmpp.util.xmlEncode
Real-World Exposure
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.
dojoxnpmDescription
Impact
What kind of vulnerability is it? Who is impacted?
Potential XSS vulnerability for users of dojox/xmpp and dojox/dtl.
Patches
Has the problem been patched? What versions should users upgrade to?
Yes, patches are available for the 1.11 through 1.16 versions. Users should upgrade to one of these versions of Dojo:
- 1.16.1
- 1.15.2
- 1.14.5
- 1.13.6
- 1.12.7
- 1.11.9
Users of Dojo 1.10.x and earlier should review this change and determine if it impacts them, and backport the change as appropriate.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
The change applied in https://github.com/dojo/dojox/pull/315 could get added separately as a patch.
For more information
If you have any questions or comments about this advisory:
- Open an issue in dojo/dojox
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | dojox | all versions | 1.11.9 |
| 📦npm | dojox | ≥ 1.12.0&&< 1.12.7 | 1.12.7 |
| 📦npm | dojox | ≥ 1.13.0&&< 1.13.6 | 1.13.6 |
| 📦npm | dojox | ≥ 1.14.0&&< 1.14.5 | 1.14.5 |
| 📦npm | dojox | ≥ 1.15.0&&< 1.15.2 | 1.15.2 |
| 📦npm | dojox | ≥ 1.16.0&&< 1.16.1 | 1.16.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dojox. 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 dojox to 1.11.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pg97-ww7h-5mjr 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-pg97-ww7h-5mjr 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-pg97-ww7h-5mjr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is GHSA-pg97-ww7h-5mjr in your dependencies?
O3 detects GHSA-pg97-ww7h-5mjr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.