How severe is CVE-2010-1330?

No CVSS score has been assigned to CVE-2010-1330 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-1330?

CVE-2010-1330 affects the following packages: org.jruby:jruby-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2010-1330?

Update org.jruby:jruby-core to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-1330 is resolved across your whole dependency graph.

How do I detect CVE-2010-1330 in my Maven dependencies?

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

How do I mitigate CVE-2010-1330 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-2010-1330 actively exploited in the wild?

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

CVE-2010-1330 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th 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.

What type of vulnerability is CVE-2010-1330?

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

CVE-2010-1330 was published on November 23, 2012 and was last updated on April 10, 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

Not in CISA KEV

CVE-2010-1330 — jruby-core

CVE-2010-1330 is a Cross-site Scripting (XSS) vulnerability in org.jruby:jruby-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.jruby:jruby-core — see the affected versions and patch details below.

Cross-site Scripting in in JRuby

Also known asGHSA-wmq2-jc9m-xp4m

Published

Nov 23, 2012

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.jruby:jruby-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The regular expression engine in JRuby before 1.4.1, when $KCODE is set to 'u', does not properly handle characters immediately after a UTF-8 character, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted string.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jruby:jruby-core`	all versions	1.4.1`org.jruby:jruby-core:1.4.1`

Affected Products

1 product · 35 configurations

Application

jrubyjruby

≤ 1.4.0

20 versions

0.9.00.9.10.9.20.9.80.9.91.0.01.0.11.0.21.0.31.11.1.11.1.2

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.

The regular expression engine in JRuby before 1.4.1, when $KCODE is set …

jruby.orgNVDJan 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.jruby:jruby-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jruby:jruby-core to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-1330 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

RHSA-2011:1456Red Hat JBoss SOA Platform 5.1

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2010-1330 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works