What is CVE-2021-41182?

### 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: ```js $( "#datepicker" ).datepicker( { altField: " ", } ); ``` 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 inform

How severe is CVE-2021-41182?

CVE-2021-41182 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-41182?

CVE-2021-41182 affects the following packages: org.webjars.npm:jquery-ui (Maven), jquery-ui (npm), jQuery.UI.Combined (NuGet), jquery-ui-rails (RubyGems). Ecosystems affected: Maven, npm, NuGet, RubyGems.

How do I fix CVE-2021-41182?

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

How do I detect CVE-2021-41182 in my Maven, npm, NuGet, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:jquery-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-41182 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2021-41182 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2021-41182, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-41182?

CVE-2021-41182 has an EPSS (Exploit Prediction Scoring System) score of 39.4%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2021-41182?

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

When was CVE-2021-41182 published, and has it been updated?

CVE-2021-41182 was published on October 26, 2021 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven📦 npm.NET NuGet💎 RubyGems

Not in CISA KEV

MEDIUM severity

CVE-2021-41182 — jquery-ui

MEDIUMFix: jquery/jquery-ui#1954

CVE-2021-41182 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.webjars.npm:jquery-ui. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.webjars.npm:jquery-ui — see the affected versions and patch details below.

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

Also known asBIT-drupal-2021-41182GHSA-9gj3-hwp5-pmwc

Published

Oct 26, 2021

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

39.4%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

696other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

jquery-uinpm

970Kdownloads / week

Description

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 Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.webjars.npm:jquery-ui`	all versions	1.13.0`org.webjars.npm:jquery-ui:1.13.0`
📦npm	`jquery-ui`	all versions	1.13.0`npm install jquery-ui@1.13.0`
.NETNuGet	`jQuery.UI.Combined`	all versions	1.13.0`dotnet add package jQuery.UI.Combined --version 1.13.0`
💎RubyGems	`jquery-ui-rails`	all versions	7.0.0`bundle update jquery-ui-rails --conservative`

Affected Products

29 products · 64 configurations

debian linuxdebian

1 version

9.0

Application

drupaldrupal

≥ 7.0 && < 7.86

range

fedorafedoraproject

4 versions

33343536

Application

jquery uijqueryui

< 1.13.0

range

h300e firmwarenetapp

all

h300s firmwarenetapp

all

Exploits & PoCs

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

jQuery-UI is the official jQuery user interface library. Prior to versio…

github.comNVDOct 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars.npm:jquery-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.webjars.npm:jquery-ui to 1.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-41182 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Virtualization Engine 4.4	`org.ovirt.engine-root-0:4.5.0.7-9`	RHSA-2022:4711

Frequently Asked Questions

### 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: ```js $( "#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 inform

O3 Security · Impact-Aware SCA

Is CVE-2021-41182 in your dependencies?

Find it across Maven, npm, NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works