How severe is GHSA-w992-2gmj-9xxj?

No CVSS score has been assigned to GHSA-w992-2gmj-9xxj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w992-2gmj-9xxj?

GHSA-w992-2gmj-9xxj affects the following packages: swagger-ui (npm). Ecosystems affected: npm.

How do I fix GHSA-w992-2gmj-9xxj?

Update swagger-ui to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w992-2gmj-9xxj is resolved across your whole dependency graph.

How do I detect GHSA-w992-2gmj-9xxj in my npm dependencies?

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

How do I mitigate GHSA-w992-2gmj-9xxj 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-w992-2gmj-9xxj actively exploited in the wild?

No public exploit code has been indexed for GHSA-w992-2gmj-9xxj 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-w992-2gmj-9xxj published, and has it been updated?

GHSA-w992-2gmj-9xxj 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 swagger-uiGHSA-w992-2gmj-9xxj

GHSA-w992-2gmj-9xxj is a security vulnerability in swagger-ui. A fix is available for swagger-ui — 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.

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

swagger-uinpm

174Kdownloads / week

Description

Versions of swagger-ui prior to 2.2.1 are vulnerable to Cross-Site Scripting (XSS). The package allows HTML code in the swagger.apiInfo.description value without proper sanitization, which may allow attackers to execute arbitrary JavaScript.

Recommendation

Upgrade to version 2.2.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`swagger-ui`	all versions	2.2.1`npm install swagger-ui@2.2.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for swagger-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update swagger-ui to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w992-2gmj-9xxj 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 `swagger-ui` prior to 2.2.1 are vulnerable to Cross-Site Scripting (XSS). The package allows HTML code in the `swagger.apiInfo.description` value without proper sanitization, which may allow attackers to execute arbitrary JavaScript. ## Recommendation Upgrade to version 2.2.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-w992-2gmj-9xxj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works