Skip to content
Noroxi

easyXDM vulnerabilitieseasyXDM: known vulnerabilities and safe versions

npm: easyxdm

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

By branch: 2.x is safe from 2.5.0.

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——4medium2.5.0

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-52122020-02-13

    Cross-site Scripting (XSS) in EasyXDM before 2.4.18 allows remote attackers to inject arbitrary web script or html via the easyxdm.swf file.

    Affected versions: < 2.4.18

    medium 6.1

    Fixed in: 2.4.18

  • CVE-2014-14032014-02-05

    Cross-site scripting (XSS) vulnerability in name.html in easyXDM before 2.4.19 allows remote attackers to inject arbitrary web script or HTM

    Affected versions: < 2.4.19

    medium 4.3

    Fixed in: 2.4.19

    EPSS 1.8%

  • no CVE

    This tightens down the default origin whitelist in the CORS example.

    Affected versions: < 2.5.0

    medium

    Fixed in: 2.5.0

  • no CVE

    This release fixes a potential XSS for IE running in compatibility mode.

    Affected versions: < 2.4.20

    medium

    Fixed in: 2.4.20

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 19, 2026.

Other libraries