jquery-ui-rails

Version	Released
`8.0.0` major	Apr 30, 2025
`7.0.0` major 1 CVE	Mar 19, 2024
`6.0.1` patch 4 CVEs	Dec 01, 2016
`6.0.0` major 4 CVEs	Nov 29, 2016
`5.0.5` patch 5 CVEs	May 12, 2015
`5.0.4` patch 5 CVEs	May 12, 2015
`5.0.3` patch 5 CVEs	Nov 30, 2014
`5.0.2` patch 5 CVEs	Oct 17, 2014
`5.0.1` patch 5 CVEs	Oct 10, 2014
`5.0.0` major 5 CVEs	Jul 03, 2014
`4.2.1` patch 5 CVEs	Apr 17, 2014
`4.1.2` patch 5 CVEs	Feb 18, 2014
`4.2.0` minor 5 CVEs	Feb 18, 2014
`4.1.1` patch 5 CVEs	Dec 15, 2013
`4.1.0` minor 5 CVEs	Oct 25, 2013
`4.0.5` patch 5 CVEs	Sep 21, 2013
`4.0.4` patch 5 CVEs	Jul 25, 2013
`4.0.3` patch 5 CVEs	May 18, 2013
`4.0.2` patch 5 CVEs	Mar 15, 2013
`4.0.1` patch 5 CVEs	Feb 07, 2013
`4.0.0` major 5 CVEs	Feb 04, 2013
`3.0.1` patch 7 CVEs	Jan 10, 2013
`3.0.0` major 7 CVEs	Dec 26, 2012
`2.0.2` patch 7 CVEs	Sep 29, 2012
`2.0.1` patch 7 CVEs	Sep 24, 2012
`2.0.0` major 7 CVEs	Aug 22, 2012
`1.1.1` patch 7 CVEs	Aug 16, 2012
`1.1.0` minor 7 CVEs	Jul 25, 2012
`1.0.0` major 7 CVEs	Jun 08, 2012
`0.5.0` minor 7 CVEs	Jun 06, 2012
`0.4.1` patch 7 CVEs	May 30, 2012
`0.4.0` minor 7 CVEs	May 01, 2012
`0.3.0` minor 7 CVEs	Apr 20, 2012
`0.2.2` patch 7 CVEs	Feb 27, 2012
`0.2.1` patch 7 CVEs	Feb 23, 2012
`0.2.0` minor 7 CVEs	Feb 22, 2012
`0.1.0` minor 7 CVEs	Feb 20, 2012
`0.0.2` patch 7 CVEs	Feb 17, 2012
`0.0.1` initial 7 CVEs	Feb 14, 2012

8.0.0 major

Apr 30, 2025

7.0.0 major

1 CVE

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

Mar 19, 2024

6.0.1 patch

4 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Dec 01, 2016

6.0.0 major

4 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

Nov 29, 2016

5.0.5 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

May 12, 2015

5.0.4 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

May 12, 2015

5.0.3 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Nov 30, 2014

5.0.2 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Oct 17, 2014

5.0.1 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Oct 10, 2014

5.0.0 major

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Jul 03, 2014

4.2.1 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Apr 17, 2014

4.1.2 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 18, 2014

4.2.0 minor

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 18, 2014

4.1.1 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Dec 15, 2013

4.1.0 minor

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Oct 25, 2013

4.0.5 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Sep 21, 2013

4.0.4 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Jul 25, 2013

4.0.3 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

May 18, 2013

4.0.2 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Mar 15, 2013

4.0.1 patch

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 07, 2013

4.0.0 major

5 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 04, 2013

3.0.1 patch

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Jan 10, 2013

3.0.0 major

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Dec 26, 2012

2.0.2 patch

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Sep 29, 2012

2.0.1 patch

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Sep 24, 2012

2.0.0 major

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Aug 22, 2012

1.1.1 patch

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Aug 16, 2012

1.1.0 minor

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Jul 25, 2012

1.0.0 major

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Jun 08, 2012

0.5.0 minor

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Jun 06, 2012

0.4.1 patch

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

May 30, 2012

0.4.0 minor

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

May 01, 2012

0.3.0 minor

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Apr 20, 2012

0.2.2 patch

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 27, 2012

0.2.1 patch

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 23, 2012

0.2.0 minor

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 22, 2012

0.1.0 minor

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 20, 2012

0.0.2 patch

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 17, 2012

0.0.1 initial

7 CVEs

CVE-2022-31160 GHSA-h6gj-6jjq-h8g9 Jul 18, 2022

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

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Impact

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.

Patches

The bug has been patched in jQuery UI 1.13.2.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 26 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1


            7.0.0

Fixed in


          8.0.0

References

Updated Jul 21, 2025 · Source: OSV.dev

CVE-2021-41183 GHSA-j7qv-pgf6-hvh4 BIT-drupal-2021-41183 Oct 26, 2021

XSS in `*Text` options of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of various *Text options of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	showButtonPanel: true,
	showOn: "both",
	closeText: "<script>doEvilThing( 'closeText XSS' )</script>",
	currentText: "<script>doEvilThing( 'currentText XSS' )</script>",
	prevText: "<script>doEvilThing( 'prevText XSS' )</script>",
	nextText: "<script>doEvilThing( 'nextText XSS' )</script>",
	buttonText: "<script>doEvilThing( 'buttonText XSS' )</script>",
	appendText: "<script>doEvilThing( 'appendText XSS' )</script>",
} );

will call doEvilThing with 6 different parameters coming from all *Text options.

Patches

The issue is fixed in jQuery UI 1.13.0. The values passed to various *Text options are now always treated as pure text, not HTML.

Workarounds

A workaround is to not accept the value of the *Text options from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41184 GHSA-gpqq-952q-5327 BIT-drupal-2021-41184 Oct 26, 2021

XSS in the `of` option of the `.position()` util in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the of option of the .position() util from untrusted sources may execute untrusted code. For example, invoking the following code:

$( "#element" ).position( {
	my: "left top",
	at: "right bottom",
	of: "<img onerror='doEvilThing()' src='/404' />",
	collision: "none"
} );

will call the doEvilThing() function.

Patches

The issue is fixed in jQuery UI 1.13.0. Any string value passed to the of option is now treated as a CSS selector.

Workarounds

A workaround is to not accept the value of the of option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2021-41182 GHSA-9gj3-hwp5-pmwc BIT-drupal-2021-41182 Oct 26, 2021

XSS in the `altField` option of the Datepicker widget in jquery-ui

6.5 / 10

Medium

Network Low None Required Unchanged None High None

Impact

Accepting the value of the altField option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:

$( "#datepicker" ).datepicker( {
	altField: "<img onerror='doEvilThing()' src='/404' />",
} );

will call the doEvilThing function.

Patches

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.

Workarounds

A workaround is to not accept the value of the altField option from untrusted sources.

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.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 25 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5


            6.0.0


            6.0.1

Fixed in


          7.0.0

References

Updated Jul 08, 2026 · Source: OSV.dev

CVE-2010-5312 GHSA-wcm2-9c89-wmfm Oct 24, 2017

Cross-site Scripting in jquery-ui

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the Dialog widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title option.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2012-6662 GHSA-qqxp-xp9v-vvx6 Oct 24, 2017

jquery-ui Tooltip widget vulnerable to XSS

Medium

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 versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 6 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1

Fixed in


          4.0.0

References

Updated Apr 14, 2025 · Source: OSV.dev

CVE-2016-7103 GHSA-hpcf-8vf9-q4gj Oct 24, 2017

jQuery-UI vulnerable to Cross-site Scripting in dialog closeText

6.1 / 10

Medium

Network Low None Required Changed Low Low None

Affected versions of jquery-ui are vulnerable to a cross-site scripting vulnerability when arbitrary user input is supplied as the value of the closeText parameter in the dialog function.

jQuery-UI is a library for manipulating UI elements via jQuery.

Version 1.11.4 has a cross site scripting (XSS) vulnerability in the closeText parameter of the dialog function. If your application passes user input to this parameter, it may be vulnerable to XSS via this attack vector.

Recommendation

Upgrade to jQuery-UI 1.12.0 or later.

Affected versions


          0.0.1


          0.0.2


          0.1.0


          0.2.0


          0.2.1


          0.2.2


          0.3.0


          0.4.0


          0.4.1


          0.5.0


          1.0.0


          1.1.0

+ 23 more


            1.1.1


            2.0.0


            2.0.1


            2.0.2


            3.0.0


            3.0.1


            4.0.0


            4.0.1


            4.0.2


            4.0.3


            4.0.4


            4.0.5


            4.1.0


            4.1.1


            4.1.2


            4.2.0


            4.2.1


            5.0.0


            5.0.1


            5.0.2


            5.0.3


            5.0.4


            5.0.5

Fixed in


          6.0.0

References

Updated Mar 11, 2024 · Source: OSV.dev

Feb 14, 2012

Activity

Details