What is CVE-2013-2022?

CVE-2013-2022 is a medium-severity cross-site scripting (XSS) vulnerability in jplayer (npm), affecting versions < 2.3.0. It is fixed in 2.3.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of jplayer are affected by CVE-2013-2022?

jplayer (npm) versions < 2.3.0 is affected.

Is there a fix for CVE-2013-2022?

Yes. CVE-2013-2022 is fixed in 2.3.0. Upgrade to this version or later.

Is CVE-2013-2022 exploitable, and should I be worried?

Whether CVE-2013-2022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2013-2022 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2013-2022 in jplayer

Q: Which versions of jplayer are affected by CVE-2013-2022?

jplayer (npm) versions < 2.3.0 is affected.

Q: Is there a fix for CVE-2013-2022?

Yes. CVE-2013-2022 is fixed in 2.3.0. Upgrade to this version or later.

Q: Is CVE-2013-2022 exploitable, and should I be worried?

Whether CVE-2013-2022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2013-2022 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2013-2022?

Upgrade jplayer to 2.3.0 or later.

Summary

jplayer Cross Site Scripting vulnerability

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.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

jplayer (< 2.3.0)

Security releases

jplayer → 2.3.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade jplayer to 2.3.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2013-2022? CVE-2013-2022 is a medium-severity cross-site scripting (XSS) vulnerability in jplayer (npm), affecting versions < 2.3.0. It is fixed in 2.3.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of jplayer are affected by CVE-2013-2022? jplayer (npm) versions < 2.3.0 is affected.
Is there a fix for CVE-2013-2022? Yes. CVE-2013-2022 is fixed in 2.3.0. Upgrade to this version or later.
Is CVE-2013-2022 exploitable, and should I be worried? Whether CVE-2013-2022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2013-2022 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2013-2022? Upgrade jplayer to 2.3.0 or later.