How severe is GHSA-j8r2-2x94-2q67?

No CVSS score has been assigned to GHSA-j8r2-2x94-2q67 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j8r2-2x94-2q67?

GHSA-j8r2-2x94-2q67 affects the following packages: diagram-js-direct-editing (npm). Ecosystems affected: npm.

How do I fix GHSA-j8r2-2x94-2q67?

Update diagram-js-direct-editing to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8r2-2x94-2q67 is resolved across your whole dependency graph.

How do I detect GHSA-j8r2-2x94-2q67 in my npm dependencies?

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

How do I mitigate GHSA-j8r2-2x94-2q67 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-j8r2-2x94-2q67 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j8r2-2x94-2q67 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-j8r2-2x94-2q67 published, and has it been updated?

GHSA-j8r2-2x94-2q67 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-js-direct-editingGHSA-j8r2-2x94-2q67

GHSA-j8r2-2x94-2q67 is a security vulnerability in diagram-js-direct-editing. A fix is available for diagram-js-direct-editing — see the affected versions and patch details below.

Published

Sep 11, 2020

Updated

Sep 28, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg 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.

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

diagram-js-direct-editingnpm

304Kdownloads / week

Description

Versions of diagram-js-direct-editing prior to 1.4.3 are vulnerable to Cross-Site Scripting. The package fails to sanitize input from the clipboard, allowing attackers to execute arbitrary JavaScript in the victim's browser.

Recommendation

Upgrade to version 1.4.3 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`diagram-js-direct-editing`	all versions	1.4.3`npm install diagram-js-direct-editing@1.4.3`

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-direct-editing, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update diagram-js-direct-editing to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8r2-2x94-2q67 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-direct-editing` prior to 1.4.3 are vulnerable to Cross-Site Scripting. The package fails to sanitize input from the clipboard, allowing attackers to execute arbitrary JavaScript in the victim's browser. ## Recommendation Upgrade to version 1.4.3 or later.

O3 Security · Impact-Aware SCA

Is GHSA-j8r2-2x94-2q67 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works