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. 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-j8r2-2x94-2q67 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-j8r2-2x94-2q67?

O3 pinpoints whether GHSA-j8r2-2x94-2q67 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-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

GHSA-j8r2-2x94-2q67

GHSA-j8r2-2x94-2q67 is a security vulnerability in diagram-js-direct-editing. O3 Security confirms whether GHSA-j8r2-2x94-2q67 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in diagram-js-direct-editing

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

📦diagram-js-direct-editing

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

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. 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-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
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-j8r2-2x94-2q67 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-j8r2-2x94-2q67. 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-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?

O3 detects GHSA-j8r2-2x94-2q67 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