\",\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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match."}},{"@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":"If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands."}},{"@type":"Question","name":"How does O3 Security protect against GHSA-j7qv-pgf6-hvh4?","acceptedAnswer":{"@type":"Answer","text":"O3 pinpoints whether GHSA-j7qv-pgf6-hvh4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed."}},{"@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 7.9%, placing it in the 94th 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 March 13, 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

GHSA-j7qv-pgf6-hvh4

MEDIUM

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

Also known asBIT-drupal-2021-41183CVE-2021-41183
Published
Oct 26, 2021
Updated
Mar 13, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
7.9%probability of exploitation in next 30 days
Lower Risk94th percentile+5.03%
1.41%4.09%6.78%9.46%5.3%7.9%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

jquery-uinpm
977Kdownloads / 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.0
📦npmjquery-uiall versions1.13.0
.NETNuGetjQuery.UI.Combinedall versions1.13.0
💎RubyGemsjquery-ui-railsall versions7.0.0
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-j7qv-pgf6-hvh4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-j7qv-pgf6-hvh4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-j7qv-pgf6-hvh4 across Maven, npm, NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works