How severe is GHSA-788m-pj96-7w2c?

No CVSS score has been assigned to GHSA-788m-pj96-7w2c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-788m-pj96-7w2c?

GHSA-788m-pj96-7w2c affects the following packages: fomantic-ui (npm). Ecosystems affected: npm.

How do I fix GHSA-788m-pj96-7w2c?

Update fomantic-ui to 2.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-788m-pj96-7w2c is resolved across your whole dependency graph.

How do I detect GHSA-788m-pj96-7w2c in my npm dependencies?

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

How do I mitigate GHSA-788m-pj96-7w2c 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-788m-pj96-7w2c actively exploited in the wild?

No public exploit code has been indexed for GHSA-788m-pj96-7w2c 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-788m-pj96-7w2c published, and has it been updated?

GHSA-788m-pj96-7w2c 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 fomantic-uiGHSA-788m-pj96-7w2c

GHSA-788m-pj96-7w2c is a security vulnerability in fomantic-ui. A fix is available for fomantic-ui — 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.

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

fomantic-uinpm

16Kdownloads / week

Description

Versions of fomantic-ui 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

Upgrade to version 2.7.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`fomantic-ui`	all versions	2.7.0`npm install fomantic-ui@2.7.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fomantic-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fomantic-ui to 2.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-788m-pj96-7w2c 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 `fomantic-ui` 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 Upgrade to version 2.7.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-788m-pj96-7w2c in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works