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. 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-8fw4-xh83-3j6q 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-8fw4-xh83-3j6q?

O3 pinpoints whether GHSA-8fw4-xh83-3j6q 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-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

GHSA-8fw4-xh83-3j6q

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

GHSA-8fw4-xh83-3j6q is a security vulnerability in diagram-js. O3 Security confirms whether GHSA-8fw4-xh83-3j6q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in diagram-js

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

📦diagram-js📦diagram-js

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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	`diagram-js`	≥ 3.0.0&&< 3.3.1	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. 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 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
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-8fw4-xh83-3j6q 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-8fw4-xh83-3j6q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-8fw4-xh83-3j6q 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