How severe is GHSA-qqxp-xp9v-vvx6?

No CVSS score has been assigned to GHSA-qqxp-xp9v-vvx6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qqxp-xp9v-vvx6?

GHSA-qqxp-xp9v-vvx6 affects the following packages: org.webjars.npm:jquery-ui (Maven), jquery-ui (npm), jQuery.UI.Combined (NuGet), jquery-ui-rails (RubyGems). Ecosystems affected: Maven, npm, NuGet, RubyGems.

How do I fix GHSA-qqxp-xp9v-vvx6?

Update org.webjars.npm:jquery-ui to 1.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqxp-xp9v-vvx6 is resolved across your whole dependency graph.

How do I detect GHSA-qqxp-xp9v-vvx6 in my Maven, npm, NuGet, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:jquery-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-qqxp-xp9v-vvx6 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-qqxp-xp9v-vvx6?

O3 pinpoints whether GHSA-qqxp-xp9v-vvx6 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-qqxp-xp9v-vvx6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qqxp-xp9v-vvx6 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.

What type of vulnerability is GHSA-qqxp-xp9v-vvx6?

GHSA-qqxp-xp9v-vvx6 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-qqxp-xp9v-vvx6 published, and has it been updated?

GHSA-qqxp-xp9v-vvx6 was published on October 24, 2017 and was last updated on April 14, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven📦 npm.NET NuGet💎 RubyGems

GHSA-qqxp-xp9v-vvx6

Fix: jquery/jquery-ui@5fee6fd

GHSA-qqxp-xp9v-vvx6 is a Cross-site Scripting (XSS) vulnerability in org.webjars.npm:jquery-ui. O3 Security confirms whether GHSA-qqxp-xp9v-vvx6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

jquery-ui Tooltip widget vulnerable to XSS

Also known asCVE-2012-6662

Published

Oct 24, 2017

Updated

Apr 14, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Real-World Exposure

4 pkgs 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-uinpm

933Kdownloads / week

Description

Cross-site scripting (XSS) vulnerability in the default content option in jquery.ui.tooltip.js in the Tooltip widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title attribute, which is not properly handled in the autocomplete combo box demo.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.webjars.npm:jquery-ui`	all versions	1.10.0
📦npm	`jquery-ui`	all versions	1.10.0
.NETNuGet	`jQuery.UI.Combined`	all versions	1.10.0
💎RubyGems	`jquery-ui-rails`	all versions	4.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:jquery-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 org.webjars.npm:jquery-ui to 1.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqxp-xp9v-vvx6 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-qqxp-xp9v-vvx6 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-qqxp-xp9v-vvx6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-qqxp-xp9v-vvx6 in your dependencies?

O3 detects GHSA-qqxp-xp9v-vvx6 across Maven, npm, NuGet 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