How severe is GHSA-fj93-7wm4-8x2g?

No CVSS score has been assigned to GHSA-fj93-7wm4-8x2g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fj93-7wm4-8x2g?

GHSA-fj93-7wm4-8x2g affects the following packages: jquery-mobile (npm). Ecosystems affected: npm.

How do I fix GHSA-fj93-7wm4-8x2g?

No patched version of jquery-mobile has shipped for GHSA-fj93-7wm4-8x2g 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-fj93-7wm4-8x2g in my npm dependencies?

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

How do I mitigate GHSA-fj93-7wm4-8x2g 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-fj93-7wm4-8x2g actively exploited in the wild?

No public exploit code has been indexed for GHSA-fj93-7wm4-8x2g 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-fj93-7wm4-8x2g published, and has it been updated?

GHSA-fj93-7wm4-8x2g 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 jquery-mobileGHSA-fj93-7wm4-8x2g

Fix: jquery/jquery-mobile#8649

GHSA-fj93-7wm4-8x2g is a security vulnerability in jquery-mobile. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 2, 2020

Updated

Sep 27, 2021

Affected

1 pkg

Patched

See advisory

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, a proxy for how much of the ecosystem is exposed.

jquery-mobilenpm

2Kdownloads / week

Description

All version of jquery-mobile are vulnerable to Cross-Site Scripting. The package checks for content in location.hash and if a URL is found it does an XmlHttpRequest (XHR) to the URL and renders the response with innerHTML. It fails to validate the Content-Type of the response, allowing attackers to include malicious payloads as part of query parameters that are reflected back to the user. A response such as {"q":"<iframe/src='javascript:alert(1)'></iframe>","results":[]} would be parsed as HTML and the JavaScript payload executed.

Recommendation

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

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`jquery-mobile`	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 jquery-mobile, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of jquery-mobile has shipped for GHSA-fj93-7wm4-8x2g 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 version of `jquery-mobile` are vulnerable to Cross-Site Scripting. The package checks for content in `location.hash` and if a URL is found it does an XmlHttpRequest (XHR) to the URL and renders the response with `innerHTML`. It fails to validate the `Content-Type` of the response, allowing attackers to include malicious payloads as part of query parameters that are reflected back to the user. A response such as `{"q":"<iframe/src='javascript:alert(1)'></iframe>","results":[]}` would be parsed as HTML and the JavaScript payload executed. ## Recommendation No fix is currently available. C

O3 Security · Impact-Aware SCA

Is GHSA-fj93-7wm4-8x2g in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works