How severe is CVE-2010-5312?

CVE-2010-5312 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-2010-5312?

CVE-2010-5312 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-2010-5312?

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.

How do I detect CVE-2010-5312 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-2010-5312 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2010-5312?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2010-5312 can be triaged on real exposure rather than presence alone.

Is CVE-2010-5312 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2010-5312, 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-2010-5312?

CVE-2010-5312 has an EPSS (Exploit Prediction Scoring System) score of 18.4%, placing it in the 97th 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-2010-5312?

CVE-2010-5312 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-2010-5312 published, and has it been updated?

CVE-2010-5312 was published on November 24, 2014 and was last updated on April 16, 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-2010-5312 — jquery-ui

MEDIUMFix: jquery/jquery-ui@7e9060c

CVE-2010-5312 is a medium-severity (CVSS 6.1) 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.

Cross-site Scripting in jquery-ui

Also known asGHSA-wcm2-9c89-wmfm

Published

Nov 24, 2014

Updated

Apr 16, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

18.4%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

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.

How urgent is this, really

CVE-2010-5312 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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.

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

jquery-uinpm

595Kdownloads / week

Description

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

4 total 4 fixed

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

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.

Cross-site scripting (XSS) vulnerability in jquery.ui.dialog.js in the D…

bugs.jqueryui.comNVDApr 2019

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.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
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2010-5312 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2010-5312. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 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

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.

O3 Security · Impact-Aware SCA

Is CVE-2010-5312 in your dependencies?

O3 Security finds CVE-2010-5312 across Maven, npm, NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works