How severe is CVE-2014-0013?

CVE-2014-0013 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2014-0013?

CVE-2014-0013 affects the following packages: ember-source (RubyGems), ember-source (RubyGems), ember-source (RubyGems), ember-source (RubyGems), ember-source (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2014-0013?

Update ember-source to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0013 is resolved across your whole dependency graph.

How do I detect CVE-2014-0013 in my RubyGems dependencies?

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

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

No public exploit code has been indexed for CVE-2014-0013 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-2014-0013?

CVE-2014-0013 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th 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-2014-0013?

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

CVE-2014-0013 was published on May 14, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

MEDIUM severity

CVE-2014-0013 — ember-source

MEDIUM

CVE-2014-0013 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in ember-source. A fix is available for ember-source — see the affected versions and patch details below.

Ember.js Cross-site Scripting vulnerability

Published

May 14, 2022

Updated

Nov 8, 2023

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

💎ember-source💎ember-source💎ember-source💎ember-source💎ember-source

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Ember.js 1.0.x before 1.0.1, 1.1.x before 1.1.3, 1.2.x before 1.2.1, 1.3.x before 1.3.1, and 1.4.x before 1.4.0-beta.2 allows remote attackers to conduct cross-site scripting (XSS) attacks by leveraging an application that contains templates whose context is set to a user-supplied primitive value and also contain the {{this}} special Handlebars variable.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`ember-source`	≥ 1.0.0.pre4.0&&< 1.0.1	1.0.1`bundle update ember-source --conservative`
💎RubyGems	`ember-source`	≥ 1.1.0&&< 1.1.3	1.1.3`bundle update ember-source --conservative`
💎RubyGems	`ember-source`	≥ 1.2.0.beta.1&&< 1.2.1	1.2.1`bundle update ember-source --conservative`
💎RubyGems	`ember-source`	≥ 1.3.0.beta.1&&< 1.3.1	1.3.1`bundle update ember-source --conservative`
💎RubyGems	`ember-source`	≥ 1.4.0-beta.1&&< 1.4.0-beta.2	1.4.0-beta.2`bundle update ember-source --conservative`

Affected Products

1 product · 38 configurations

Application

ember.jsemberjs

7 versions

1.0.01.1.01.1.11.1.21.2.01.3.01.4.0

Detection & mitigation playbook

Open-source dependency

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

O3 Security · Impact-Aware SCA

Is CVE-2014-0013 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

ember.js

6.7/10

Code-Review8/10

Maintained10/10

Branch-Protection5/10

Assessed Nov 2, 2026

Timeline

Disclosed

May 14, 2022

Last updated

Nov 8, 2023

Identifiers

CVE-2014-0013

References

Advisorynvd.nist.gov · CVE 2014 0013 Webgroups.google.com · forum Webemberjs.com · ember security releases Packagegithub.com · ember.js

Related vulnerabilities

Also affects ember-source

This CVE is medium severity; 4 of 5 other CVEs affecting ember-source are rated as high or higher (top: moderate).

CVE-2013-4170CVE-2014-0014CVE-2014-0046CVE-2015-7565CVE-2015-1866

Same weakness: CWE-79

This CVE is medium severity; 3 of 3 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-44267CVE-2026-96632CVE-2026-9086Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 8, 2023