\",\n\tcurrentText: \"\",\n\tprevText: \"\",\n\tnextText: \"\",\n\tcurrentText: \"\",\n\tprevText: \"\",\n\tnextText: \"\",\n\tcurrentText: \"\",\n\tprevText: \"\",\n\tnextText: \"\",\n\tbuttonText: \"\",\n\tappen"}},{"@type":"Question","name":"How severe is GHSA-j7qv-pgf6-hvh4?","acceptedAnswer":{"@type":"Answer","text":"GHSA-j7qv-pgf6-hvh4 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance."}},{"@type":"Question","name":"Which packages are affected by GHSA-j7qv-pgf6-hvh4?","acceptedAnswer":{"@type":"Answer","text":"GHSA-j7qv-pgf6-hvh4 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."}},{"@type":"Question","name":"How do I fix GHSA-j7qv-pgf6-hvh4?","acceptedAnswer":{"@type":"Answer","text":"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 GHSA-j7qv-pgf6-hvh4 is resolved across your whole dependency graph."}},{"@type":"Question","name":"How do I detect GHSA-j7qv-pgf6-hvh4 in my Maven, npm, NuGet, RubyGems dependencies?","acceptedAnswer":{"@type":"Answer","text":"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."}},{"@type":"Question","name":"How do I mitigate GHSA-j7qv-pgf6-hvh4 if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"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."}},{"@type":"Question","name":"Is GHSA-j7qv-pgf6-hvh4 actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"Yes. There are 1 known exploit references for GHSA-j7qv-pgf6-hvh4, 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."}},{"@type":"Question","name":"What is the EPSS score for GHSA-j7qv-pgf6-hvh4?","acceptedAnswer":{"@type":"Answer","text":"GHSA-j7qv-pgf6-hvh4 has an EPSS (Exploit Prediction Scoring System) score of 8.5%, placing it in the 95th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority."}},{"@type":"Question","name":"What type of vulnerability is GHSA-j7qv-pgf6-hvh4?","acceptedAnswer":{"@type":"Answer","text":"GHSA-j7qv-pgf6-hvh4 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."}},{"@type":"Question","name":"When was GHSA-j7qv-pgf6-hvh4 published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"GHSA-j7qv-pgf6-hvh4 was published on October 26, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven📦 npm.NET NuGet💎 RubyGems
Not in CISA KEV
MEDIUM severity

XSS in `*Text` options of the Datepicker widget in jquery-uiGHSA-j7qv-pgf6-hvh4

MEDIUMFix: jquery/jquery-ui#1953

GHSA-j7qv-pgf6-hvh4 is a medium-severity (CVSS 6.5) Cross-site Scripting (XSS) vulnerability in org.webjars.npm:jquery-ui. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.webjars.npm:jquery-ui — see the affected versions and patch details below.

Also known asBIT-drupal-2021-41183CVE-2021-41183
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
8.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk
1.24%4.23%7.22%10.2%2.9%8.5%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-j7qv-pgf6-hvh4 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

705other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
jquery-uinpm
759Kdownloads / week

Description

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 Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.webjars.npm:jquery-uiall versions1.13.0org.webjars.npm:jquery-ui:1.13.0
📦npmjquery-uiall versions1.13.0npm install jquery-ui@1.13.0
.NETNuGetjQuery.UI.Combinedall versions1.13.0dotnet add package jQuery.UI.Combined --version 1.13.0
💎RubyGemsjquery-ui-railsall versions7.0.0bundle update jquery-ui-rails --conservative

Affected Products

28 products · 46 configurations
OS
debian linuxdebian
1 version
9.0
Application
drupaldrupal
≥ 9.3.0 && < 9.3.3
range
OS
fedorafedoraproject
4 versions
33343536
Application
jquery uijqueryui
< 1.13.0
range
OS
h300e firmwarenetapp
all
OS
h300s firmwarenetapp
all
Exploits & PoCs
1

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

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

github.comNVDOct 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. 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 GHSA-j7qv-pgf6-hvh4 is resolved across your whole dependency graph.

  3. 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
ProductFixed inAdvisory
Red Hat Virtualization Engine 4.4org.ovirt.engine-root-0:4.5.0.7-9RHSA-2022:4711

Frequently Asked Questions

### 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: ```js $( "#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>", appen
O3 Security · Impact-Aware SCA

Is GHSA-j7qv-pgf6-hvh4 in your dependencies?

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

Scan my dependencies How O3 SCA works
XSS in `*Text` options of the Datepicker widget in jquery-ui