How severe is GHSA-8fw4-xh83-3j6q?

No CVSS score has been assigned to GHSA-8fw4-xh83-3j6q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8fw4-xh83-3j6q?

GHSA-8fw4-xh83-3j6q affects the following packages: diagram-js (npm), diagram-js (npm). Ecosystems affected: npm.

How do I fix GHSA-8fw4-xh83-3j6q?

Update diagram-js to 2.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8fw4-xh83-3j6q is resolved across your whole dependency graph.

How do I detect GHSA-8fw4-xh83-3j6q in my npm dependencies?

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

How do I mitigate GHSA-8fw4-xh83-3j6q 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-8fw4-xh83-3j6q actively exploited in the wild?

No public exploit code has been indexed for GHSA-8fw4-xh83-3j6q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8fw4-xh83-3j6q published, and has it been updated?

GHSA-8fw4-xh83-3j6q was published on September 11, 2020 and was last updated on September 28, 2021. 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 diagram-jsGHSA-8fw4-xh83-3j6q

Fix: bpmn-io/diagram-js@2565c40

GHSA-8fw4-xh83-3j6q is a security vulnerability in diagram-js. A fix is available for diagram-js — see the affected versions and patch details below.

Published

Sep 11, 2020

Updated

Sep 28, 2021

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 28, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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

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

diagram-jsnpm

404Kdownloads / week

Description

Versions of diagram-js prior to 3.3.1 (for 3.x) and 2.6.2 (for 2.x) are vulnerable to Cross-Site Scripting. The package fails to escape output of user-controlled input in search-pad, allowing attackers to execute arbitrary JavaScript.

Recommendation

If you are using diagram-js 3.x, upgrade to version 3.3.1. If you are using diagram-js 2.x, upgrade to version 2.6.2.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`diagram-js`	all versions	2.6.2`npm install diagram-js@2.6.2`
📦npm	`diagram-js`	≥ 3.0.0&&< 3.3.1	3.3.1`npm install diagram-js@3.3.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for diagram-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update diagram-js to 2.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8fw4-xh83-3j6q 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 `diagram-js` prior to 3.3.1 (for 3.x) and 2.6.2 (for 2.x) are vulnerable to Cross-Site Scripting. The package fails to escape output of user-controlled input in `search-pad`, allowing attackers to execute arbitrary JavaScript. ## Recommendation If you are using diagram-js 3.x, upgrade to version 3.3.1. If you are using diagram-js 2.x, upgrade to version 2.6.2.

O3 Security · Impact-Aware SCA

Is GHSA-8fw4-xh83-3j6q in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works