CVE-2013-2022: XSS

Published Aug 17, 2013
·
Updated

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.

Other sources

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.

GitHub

Affected Software

70 affected componentsFixes available
npm/jplayer<2.3.0
2.3.0
Happyworm Jplayer<=2.2.22
Happyworm Jplayer=0.2.1-beta
Happyworm Jplayer=0.2.2-beta
Happyworm Jplayer=0.2.3-beta
Happyworm Jplayer=0.2.4-beta
Happyworm Jplayer=0.2.5-beta
Happyworm Jplayer=1.0.0
Happyworm Jplayer=1.1.0
Happyworm Jplayer=1.1.1
Happyworm Jplayer=1.2.0
Happyworm Jplayer=2.0.0
Happyworm Jplayer=2.0.1
Happyworm Jplayer=2.0.2
Happyworm Jplayer=2.0.3
Happyworm Jplayer=2.0.4
Happyworm Jplayer=2.0.5
Happyworm Jplayer=2.0.6
Happyworm Jplayer=2.0.7
Happyworm Jplayer=2.0.8
Happyworm Jplayer=2.0.9
Happyworm Jplayer=2.0.10
Happyworm Jplayer=2.0.11
Happyworm Jplayer=2.0.12
Happyworm Jplayer=2.0.13
Happyworm Jplayer=2.0.14
Happyworm Jplayer=2.0.15
Happyworm Jplayer=2.0.16
Happyworm Jplayer=2.0.17
Happyworm Jplayer=2.0.18
Happyworm Jplayer=2.0.19
Happyworm Jplayer=2.0.20
Happyworm Jplayer=2.0.21
Happyworm Jplayer=2.0.22
Happyworm Jplayer=2.0.23
Happyworm Jplayer=2.0.24
Happyworm Jplayer=2.0.25
Happyworm Jplayer=2.0.26
Happyworm Jplayer=2.0.27
Happyworm Jplayer=2.0.28
Happyworm Jplayer=2.0.29
Happyworm Jplayer=2.0.30
Happyworm Jplayer=2.0.31
Happyworm Jplayer=2.0.32
Happyworm Jplayer=2.0.33
Happyworm Jplayer=2.0.34
Happyworm Jplayer=2.0.35
Happyworm Jplayer=2.0.36
Happyworm Jplayer=2.1.0
Happyworm Jplayer=2.1.1
Happyworm Jplayer=2.1.2
Happyworm Jplayer=2.1.3
Happyworm Jplayer=2.1.4
Happyworm Jplayer=2.1.5
Happyworm Jplayer=2.1.6
Happyworm Jplayer=2.2.0
Happyworm Jplayer=2.2.1
Happyworm Jplayer=2.2.2
Happyworm Jplayer=2.2.10
Happyworm Jplayer=2.2.11
Happyworm Jplayer=2.2.12
Happyworm Jplayer=2.2.13
Happyworm Jplayer=2.2.14
Happyworm Jplayer=2.2.15
Happyworm Jplayer=2.2.16
Happyworm Jplayer=2.2.17
Happyworm Jplayer=2.2.18
Happyworm Jplayer=2.2.19
Happyworm Jplayer=2.2.20
Happyworm Jplayer=2.2.21

Event History

Aug 17, 2013
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·04:39 AM

Frequently Asked Questions

1

What is the severity of CVE-2013-2022?

CVE-2013-2022 is classified as a high severity vulnerability due to its potential for cross-site scripting attacks.

2

How do I fix CVE-2013-2022?

To fix CVE-2013-2022, upgrade jPlayer to version 2.3.0 or later.

3

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

CVE-2013-2022 affects all versions of jPlayer prior to 2.3.0, including all beta versions from 0.2.1 to 2.2.22.

4

What types of attacks are possible with CVE-2013-2022?

CVE-2013-2022 allows remote attackers to execute arbitrary web scripts or HTML due to cross-site scripting vulnerabilities.

5

Is CVE-2013-2022 a common vulnerability?

CVE-2013-2022 is a known vulnerability affecting several releases of jPlayer, making it a relatively common issue in affected installations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203