Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven📦 npm.NET NuGet💎 RubyGems

CVE-2022-31160

MEDIUM

CVE-2022-31160 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.webjars.npm:jquery-ui. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2022-31160 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

jQuery UI contains potential XSS vulnerability when refreshing a checkboxradio with an HTML-like initial text label

Also known asGHSA-h6gj-6jjq-h8g9
Published
Jul 20, 2022
Updated
Jul 15, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known

Blast Radius

4 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

jquery-uinpm
878Kdownloads / week

Description

jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling .checkboxradio( "refresh" ) on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, someone who can change the initial HTML can wrap all the non-input contents of the label in a span.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.webjars.npm:jquery-uiall versions1.13.2
📦npmjquery-uiall versions1.13.2
.NETNuGetjQuery.UI.Combinedall versions1.13.2
💎RubyGemsjquery-ui-railsall versions8.0.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

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

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2022-31160 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 CVE-2022-31160. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, s
O3 Security · Impact-Aware SCA

Is CVE-2022-31160 in your dependencies?

O3 detects CVE-2022-31160 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.