How severe is CVE-2013-2022?

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

Which packages are affected by CVE-2013-2022?

CVE-2013-2022 affects the following packages: jplayer (npm). Ecosystems affected: npm.

How do I fix CVE-2013-2022?

Update jplayer to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2022 is resolved across your whole dependency graph.

How do I detect CVE-2013-2022 in my npm dependencies?

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

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

No public exploit code has been indexed for CVE-2013-2022 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-2022?

CVE-2013-2022 has an EPSS (Exploit Prediction Scoring System) score of 2.7%, placing it in the 86th 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-2013-2022?

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

CVE-2013-2022 was published on May 17, 2022 and was last updated on April 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2013-2022 — jplayer

Fix: happyworm/jPlayer@c5fe17b

CVE-2013-2022 is a Cross-site Scripting (XSS) vulnerability in jplayer. A fix is available for jplayer — see the affected versions and patch details below.

jplayer Cross Site Scripting vulnerability

Published

May 17, 2022

Updated

Apr 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg 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.

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

jplayernpm

17Kdownloads / week

Description

Multiple cross-site scripting (XSS) vulnerabilities in actionscript/Jplayer.as in the Flash SWF component (jplayer.swf) in jPlayer before 2.2.23 allow remote attackers to inject arbitrary web script or HTML via the (1) jQuery or (2) id parameters, a different vulnerability than CVE-2013-1942 and CVE-2013-2023, as demonstrated by using the alert function in the jQuery parameter. NOTE: these are the same parameters as CVE-2013-1942, but the fix for CVE-2013-1942 uses a blacklist for the jQuery parameter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`jplayer`	all versions	2.3.0`npm install jplayer@2.3.0`

Affected Products

1 product · 69 configurations

Application

jplayerhappyworm

≤ 2.2.22

68 versions

0.2.10.2.20.2.30.2.40.2.51.0.01.1.01.1.11.2.02.0.02.0.12.0.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jplayer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jplayer to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2022 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.

Frequently Asked Questions

Multiple cross-site scripting (XSS) vulnerabilities in actionscript/Jplayer.as in the Flash SWF component (jplayer.swf) in jPlayer before 2.3.0 allow remote attackers to inject arbitrary web script or HTML via the (1) jQuery or (2) id parameters, a different vulnerability than CVE-2013-1942 and CVE-2013-2023, as demonstrated by using the alert function in the jQuery parameter. NOTE: these are the same parameters as CVE-2013-1942, but the fix for CVE-2013-1942 uses a blacklist for the jQuery parameter.

O3 Security · Impact-Aware SCA

Is CVE-2013-2022 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works