How severe is GHSA-wp32-wq34-2rqh?

GHSA-wp32-wq34-2rqh has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-wp32-wq34-2rqh?

GHSA-wp32-wq34-2rqh affects the following packages: dijit (npm). Ecosystems affected: npm.

How do I fix GHSA-wp32-wq34-2rqh?

Update dijit to 1.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wp32-wq34-2rqh is resolved across your whole dependency graph.

How do I detect GHSA-wp32-wq34-2rqh in my npm dependencies?

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.

How do I mitigate GHSA-wp32-wq34-2rqh if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-wp32-wq34-2rqh?

O3 pinpoints whether GHSA-wp32-wq34-2rqh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wp32-wq34-2rqh actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-wp32-wq34-2rqh, including 1 in-the-wild exploitation 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-wp32-wq34-2rqh?

GHSA-wp32-wq34-2rqh has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 63th 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-wp32-wq34-2rqh?

GHSA-wp32-wq34-2rqh 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-wp32-wq34-2rqh published, and has it been updated?

GHSA-wp32-wq34-2rqh was published on May 14, 2022 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

GHSA-wp32-wq34-2rqh

MEDIUM

dijit editor cross-site scripting vulnerability

Also known asCVE-2018-6561

Published

May 14, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk63th percentile+0.95%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

dijitnpm

10Kdownloads / week

Description

dijit.Editor in Dojo Toolkit 1.13 allows XSS via the onload attribute of an SVG element.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`dijit`	all versions	1.13.1

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.

dijit.Editor in Dojo Toolkit 1.13 allows XSS via the onload attribute of…

github.comNVDFeb 2018

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update dijit to 1.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wp32-wq34-2rqh 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-wp32-wq34-2rqh 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-wp32-wq34-2rqh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

dijit.Editor in Dojo Toolkit 1.13 allows XSS via the onload attribute of an SVG element.

O3 Security · Impact-Aware SCA

Is GHSA-wp32-wq34-2rqh in your dependencies?

O3 detects GHSA-wp32-wq34-2rqh across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works