How severe is GHSA-cr56-66mx-293v?

No CVSS score has been assigned to GHSA-cr56-66mx-293v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cr56-66mx-293v?

GHSA-cr56-66mx-293v affects the following packages: @toast-ui/editor (npm). Ecosystems affected: npm.

How do I fix GHSA-cr56-66mx-293v?

Update @toast-ui/editor to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cr56-66mx-293v is resolved across your whole dependency graph.

How do I detect GHSA-cr56-66mx-293v in my npm dependencies?

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

How do I mitigate GHSA-cr56-66mx-293v 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-cr56-66mx-293v actively exploited in the wild?

No public exploit code has been indexed for GHSA-cr56-66mx-293v 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-cr56-66mx-293v published, and has it been updated?

GHSA-cr56-66mx-293v was published on September 3, 2020 and was last updated on October 4, 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 @toast-ui/editorGHSA-cr56-66mx-293v

Fix: nhn/tui.editor#1010

GHSA-cr56-66mx-293v is a security vulnerability in @toast-ui/editor. A fix is available for @toast-ui/editor — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Oct 4, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 4, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦@toast-ui/editor

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 @toast-ui/editor prior to 2.2.0 are vulnerable to Cross-Site Scripting (XSS). There are multiple bypasses to the package's built-in XSS sanitization. This may allow attackers to execute arbitrary JavaScript on a victim's browser.

Recommendation

Upgrade to version 2.2.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@toast-ui/editor`	all versions	2.2.0`npm install @toast-ui/editor@2.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @toast-ui/editor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @toast-ui/editor to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cr56-66mx-293v 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 `@toast-ui/editor` prior to 2.2.0 are vulnerable to Cross-Site Scripting (XSS). There are multiple bypasses to the package's built-in XSS sanitization. This may allow attackers to execute arbitrary JavaScript on a victim's browser. ## Recommendation Upgrade to version 2.2.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-cr56-66mx-293v in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works