How severe is GHSA-p9vv-3945-x93h?

No CVSS score has been assigned to GHSA-p9vv-3945-x93h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p9vv-3945-x93h?

GHSA-p9vv-3945-x93h affects the following packages: semantic-ui-search (npm). Ecosystems affected: npm.

How do I fix GHSA-p9vv-3945-x93h?

No patched version of semantic-ui-search has shipped for GHSA-p9vv-3945-x93h yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-p9vv-3945-x93h in my npm dependencies?

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

How do I mitigate GHSA-p9vv-3945-x93h 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-p9vv-3945-x93h actively exploited in the wild?

No public exploit code has been indexed for GHSA-p9vv-3945-x93h 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-p9vv-3945-x93h published, and has it been updated?

GHSA-p9vv-3945-x93h 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 semantic-ui-searchGHSA-p9vv-3945-x93h

GHSA-p9vv-3945-x93h is a security vulnerability in semantic-ui-search. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 2, 2020

Updated

Sep 27, 2021

Affected

1 pkg

Patched

None yet

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.

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

semantic-ui-searchnpm

193downloads / week

Description

All versions of semantic-ui-search are vulnerable to Cross-Site Scripting. Lack of output encoding on the selection dropdowns can lead to user input being executed instead of printed as text.

Recommendation

No fix is currently available. Consider using an alternative module until a fix is made available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`semantic-ui-search`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for semantic-ui-search, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of semantic-ui-search has shipped for GHSA-p9vv-3945-x93h yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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

All versions of `semantic-ui-search` are vulnerable to Cross-Site Scripting. Lack of output encoding on the selection dropdowns can lead to user input being executed instead of printed as text. ## Recommendation No fix is currently available. Consider using an alternative module until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-p9vv-3945-x93h in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works