Skip to content
Noroxi

jPlayer vulnerabilitiesjPlayer: known vulnerabilities and safe versions

npm: jplayer

jPlayer has 3 known vulnerability records: 1 in the npm advisory data (GitHub Advisory Database via OSV, the same source npm audit uses) and 2 only in Retire.js (CDN builds and advisories without a CVE).

By branch: 2.x is safe from 2.3.1.

Vulnerabilities and safe version by branch

Safe version: on that branch, this release and every later one (up to the branch's latest release, where known) fall outside every known record's range. Candidates are only the records' own fixed versions and the branch's latest release; "No fix" means moving off the branch.

BranchSupportLatest on branchRecordsSafe version
2.x——3medium2.3.1

Support dates appear only for libraries that endoflife.date tracks.

Records

Newest first. Ranges are the record's own data; several ranges mean separate fixes per branch.

  • CVE-2013-20222013-08-17

    Multiple cross-site scripting (XSS) vulnerabilities in actionscript/Jplayer.as in the Flash SWF component (jplayer.swf) in jPlayer before 2.

    Affected versions: < 2.3.0

    medium 4.3

    Fixed in: 2.3.0

    EPSS 2.7%

  • CVE-2013-20232013-08-15

    Cross-site scripting (XSS) vulnerability in actionscript/Jplayer.as in the Flash SWF component (jplayer.swf) in jPlayer before 2.3.1 allows

    Affected versions: < 2.3.1

    medium 4.3

    Fixed in: 2.3.1

    EPSS 2.8%

  • CVE-2013-1942exploit code exists2013-08-15

    Multiple cross-site scripting (XSS) vulnerabilities in actionscript/Jplayer.as in the Flash SWF component (jplayer.swf) in jPlayer before 2.

    Affected versions: < 2.2.20

    medium 4.3

    Fixed in: 2.2.20

    EPSS 5.4%

Sources and method

Ranges: GitHub Advisory Database (OSV npm export, daily) and Retire.js (Apache-2.0). Exploitation: CISA KEV, FIRST EPSS and exploit maturity from the Noroxi CVE database. Support dates: endoflife.date.

This page and the JavaScript library scan use the same matching rule: a row without bounds is not evidence, and versions are compared in one place. A record without a version range never counts as "affected" in the version check.

Data as of October 26, 2026.

Other libraries