XSS in the `altField` option of the Datepicker widget
jquery-ui
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| jquery-ui npm |
|
|
| jQuery.UI.Combined NuGet |
|
|
| jquery-ui-rails RubyGems |
jquery-ui
| Product | Affected | Fixed in |
|---|---|---|
| jquery-ui npm |
|
|
| jQuery.UI.Combined NuGet |
|
|
| jquery-ui-rails RubyGems |
< 7.0.0
|
| org.webjars.npm:jquery-ui Maven |
|
|
jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector. A workaround is to not accept the value of the `altField` option from untrusted sources.
From the CVE record · GitHub_M
The Datepicker widget may execute untrusted code when an application accepts its `altField` option value from an untrusted source. This affects applications that pass such values to Datepicker; the input does not specify authentication or user-interaction requirements.
Teams using npm jquery-ui, NuGet jQuery.UI.Combined, or Maven org.webjars.npm:jquery-ui before 1.13.0, or RubyGems jquery-ui-rails before 7.0.0, should check their applications.