CVE-2010-5312 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.
Cross-site Scripting in jquery-ui
EPSS Exploitation Probability
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
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.
jquery-uinpmDescription
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.webjars.npm:jquery-ui | ≥ 1.7.0&&< 1.10.0 | 1.10.0org.webjars.npm:jquery-ui:1.10.0 |
| 📦npm | jquery-ui | ≥ 1.7.0&&< 1.10.0 | 1.10.0npm install jquery-ui@1.10.0 |
| .NETNuGet | jQuery.UI.Combined | ≥ 1.7.0&&< 1.10.0 | 1.10.0dotnet add package jQuery.UI.Combined --version 1.10.0 |
| 💎RubyGems | jquery-ui-rails | all versions | 4.0.0bundle update jquery-ui-rails --conservative |
Affected Products
drillapachedebian linuxdebiandrupaldrupalfedorafedoraprojectjquery uijqueryuisnapcenternetappResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-5312 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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 6 | ipa-0:3.0.0-47.el6 | RHSA-2015:1462 |
| Red Hat Enterprise Linux 7 | ipa-0:4.1.0-18.el7 | RHSA-2015:0442 |
Frequently Asked Questions
Is CVE-2010-5312 in your dependencies?
Find it across Maven, npm, NuGet, including transitive dependencies.