CVE-2022-31160

jQuery UI vulnerable to XSS when refreshing a checkboxradio with an HTML-like initial text label

Workarounds

To remediate the issue, if you can change the initial HTML, you can wrap all the non-input contents of the label in a span:

<label>
	<input id="test-input">
	<span>&lt;img src=x onerror="alert(1)"&gt;</span>
</label>

References

https://blog.jqueryui.com/2022/07/jquery-ui-1-13-2-released/

For more information

If you have any questions or comments about this advisory, search for a relevant issue in the jQuery UI repo. If you don't find an answer, open a new issue.

Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. If you call .checkboxradio( "refresh" ) on such a widget and the initial HTML contained encoded HTML entities, they will erroneously get decoded. This can lead to potentially executing JavaScript code.

For example, starting with the following initial secure HTML:

<label>
	<input id="test-input">
	&lt;img src=x onerror="alert(1)"&gt;
</label>

and calling:

$( "#test-input" ).checkboxradio();
$( "#test-input" ).checkboxradio( "refresh" );

will turn the initial HTML into:

<label>
	<!-- some jQuery UI elements -->
	<input id="test-input">
	<img src=x onerror="alert(1)">
</label>

and the alert will get executed.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-31160 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.13.2, 8.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The bug has been patched in jQuery UI 1.13.2.

1. What is CVE-2022-31160? CVE-2022-31160 is a medium-severity cross-site scripting (XSS) vulnerability in jquery-ui (npm), affecting versions < 1.13.2. It is fixed in 1.13.2, 8.0.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2022-31160? CVE-2022-31160 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-31160?
   • jquery-ui (npm) (versions < 1.13.2)
   • org.webjars.npm:jquery-ui (maven) (versions < 1.13.2)
   • jQuery.UI.Combined (nuget) (versions < 1.13.2)
   • jquery-ui-rails (rubygems) (versions < 8.0.0)
4. Is there a fix for CVE-2022-31160? Yes. CVE-2022-31160 is fixed in 1.13.2, 8.0.0. Upgrade to this version or later.
5. Is CVE-2022-31160 exploitable, and should I be worried? Whether CVE-2022-31160 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31160 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31160?
   • Upgrade jquery-ui to 1.13.2 or later
   • Upgrade org.webjars.npm:jquery-ui to 1.13.2 or later
   • Upgrade jQuery.UI.Combined to 1.13.2 or later
   • Upgrade jquery-ui-rails to 8.0.0 or later

Other vulnerabilities in jquery-ui