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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-788m-pj96-7w2c if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-788m-pj96-7w2c?

O3 pinpoints whether GHSA-788m-pj96-7w2c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-788m-pj96-7w2c

GHSA-788m-pj96-7w2c is a security vulnerability in fomantic-ui. O3 Security confirms whether GHSA-788m-pj96-7w2c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in fomantic-ui

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

11Kdownloads / 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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-788m-pj96-7w2c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-788m-pj96-7w2c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-788m-pj96-7w2c across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works