How severe is GHSA-w32g-5hqp-gg6q?

No CVSS score has been assigned to GHSA-w32g-5hqp-gg6q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w32g-5hqp-gg6q?

GHSA-w32g-5hqp-gg6q affects the following packages: mermaid (npm). Ecosystems affected: npm.

How do I fix GHSA-w32g-5hqp-gg6q?

Update mermaid to 8.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w32g-5hqp-gg6q is resolved across your whole dependency graph.

How do I detect GHSA-w32g-5hqp-gg6q in my npm dependencies?

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

How do I mitigate GHSA-w32g-5hqp-gg6q 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-w32g-5hqp-gg6q actively exploited in the wild?

No public exploit code has been indexed for GHSA-w32g-5hqp-gg6q 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-w32g-5hqp-gg6q published, and has it been updated?

GHSA-w32g-5hqp-gg6q was published on September 2, 2020 and was last updated on September 27, 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 mermaidGHSA-w32g-5hqp-gg6q

GHSA-w32g-5hqp-gg6q is a security vulnerability in mermaid. A fix is available for mermaid — see the affected versions and patch details below.

Published

Sep 2, 2020

Updated

Sep 27, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 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.

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

mermaidnpm

17.3Mdownloads / week

Description

Versions of mermaid prior to 8.2.3 are vulnerable to Cross-Site Scripting. If malicious input such as A["<img src=invalid onerror=alert('XSS')></img>"] is provided to the application, it will execute the code instead of rendering it as text due to improper output encoding.

Recommendation

Upgrade to version 8.2.3 or later

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mermaid`	all versions	8.2.3`npm install mermaid@8.2.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mermaid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mermaid to 8.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w32g-5hqp-gg6q 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 `mermaid` prior to 8.2.3 are vulnerable to Cross-Site Scripting. If malicious input such as `A["<img src=invalid onerror=alert('XSS')></img>"] ` is provided to the application, it will execute the code instead of rendering it as text due to improper output encoding. ## Recommendation Upgrade to version 8.2.3 or later

O3 Security · Impact-Aware SCA

Is GHSA-w32g-5hqp-gg6q in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works