Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
LOW severity

GHSA-cxjc-r2fp-7mq6

LOWFix: dojo/dijit@462bdcd

GHSA-cxjc-r2fp-7mq6 is a low-severity (CVSS 3.7) Cross-site Scripting (XSS) vulnerability in dijit. O3 Security confirms whether GHSA-cxjc-r2fp-7mq6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-site Scripting in dijit editor's LinkDialog plugin

Also known asCVE-2020-4051
Published
Jun 15, 2020
Updated
Jul 8, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

6 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

dijitnpm
13Kdownloads / week

Description

Impact

XSS possible for users of the Dijit Editor's LinkDialog plugin

Patches

Yes, 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3

Workarounds

Users may apply the patch made in these releases.

For more information

If you have any questions or comments about this advisory, open an issue in dojo/dijit

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
📦npmdijitall versions1.11.11
📦npmdijit1.12.0&&< 1.12.91.12.9
📦npmdijit1.13.0&&< 1.13.81.13.8
📦npmdijit1.14.0&&< 1.14.71.14.7
📦npmdijit1.15.0&&< 1.15.41.15.4
📦npmdijit1.16.0&&< 1.16.31.16.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dijit. 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.

  2. Fix

    Update dijit to 1.11.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cxjc-r2fp-7mq6 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-cxjc-r2fp-7mq6 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-cxjc-r2fp-7mq6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact XSS possible for users of the Dijit Editor's LinkDialog plugin ### Patches Yes, 1.11.11, 1.12.9, 1.13.8, 1.14.7, 1.15.4, 1.16.3 ### Workarounds Users may apply the patch made in these releases. ### For more information If you have any questions or comments about this advisory, open an issue in [dojo/dijit](https://github.com/dojo/dijit/)
O3 Security · Impact-Aware SCA

Is GHSA-cxjc-r2fp-7mq6 in your dependencies?

O3 detects GHSA-cxjc-r2fp-7mq6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-cxjc-r2fp-7mq6: Cross-site Scripting in… | O3 Security