How severe is GHSA-2hwp-g4g7-mwwj?

No CVSS score has been assigned to GHSA-2hwp-g4g7-mwwj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2hwp-g4g7-mwwj?

GHSA-2hwp-g4g7-mwwj affects the following packages: jquery.terminal (npm). Ecosystems affected: npm.

How do I fix GHSA-2hwp-g4g7-mwwj?

Update jquery.terminal to 1.21.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2hwp-g4g7-mwwj is resolved across your whole dependency graph.

How do I detect GHSA-2hwp-g4g7-mwwj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jquery.terminal. 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-2hwp-g4g7-mwwj 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-2hwp-g4g7-mwwj?

O3 pinpoints whether GHSA-2hwp-g4g7-mwwj 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-2hwp-g4g7-mwwj actively exploited in the wild?

No public exploit code has been indexed for GHSA-2hwp-g4g7-mwwj 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-2hwp-g4g7-mwwj published, and has it been updated?

GHSA-2hwp-g4g7-mwwj was published on May 29, 2019 and was last updated on August 31, 2020. 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-2hwp-g4g7-mwwj

Fix: jcubic/jquery.terminal@c8b7727

GHSA-2hwp-g4g7-mwwj is a security vulnerability in jquery.terminal. O3 Security confirms whether GHSA-2hwp-g4g7-mwwj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Reflected Cross-Site Scripting in jquery.terminal

Published

May 29, 2019

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · 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.

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

jquery.terminalnpm

5Kdownloads / week

Description

Versions of jquery.terminal prior to 1.21.0 are vulnerable to Reflected Cross-Site Scripting. If the application has either of the options anyLinks or invokeMethods set to true, the application may execute arbitrary JavaScript through crafted malicious payloads due to insufficient sanitization.

Recommendation

Upgrade to version 1.21.0 or later

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`jquery.terminal`	all versions	1.21.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jquery.terminal. 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 jquery.terminal to 1.21.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2hwp-g4g7-mwwj 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-2hwp-g4g7-mwwj 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-2hwp-g4g7-mwwj. 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 `jquery.terminal` prior to 1.21.0 are vulnerable to Reflected Cross-Site Scripting. If the application has either of the options `anyLinks` or `invokeMethods` set to true, the application may execute arbitrary JavaScript through crafted malicious payloads due to insufficient sanitization. ## Recommendation Upgrade to version 1.21.0 or later

O3 Security · Impact-Aware SCA

Is GHSA-2hwp-g4g7-mwwj in your dependencies?

O3 detects GHSA-2hwp-g4g7-mwwj 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