CVE-2014-0013 — ember-source
MEDIUMCVE-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
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2014-0013 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
ember-source💎ember-source💎ember-source💎ember-source💎ember-sourceReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | ember-source | ≥ 1.0.0.pre4.0&&< 1.0.1 | 1.0.1bundle update ember-source --conservative |
| 💎RubyGems | ember-source | ≥ 1.1.0&&< 1.1.3 | 1.1.3bundle update ember-source --conservative |
| 💎RubyGems | ember-source | ≥ 1.2.0.beta.1&&< 1.2.1 | 1.2.1bundle update ember-source --conservative |
| 💎RubyGems | ember-source | ≥ 1.3.0.beta.1&&< 1.3.1 | 1.3.1bundle update ember-source --conservative |
| 💎RubyGems | ember-source | ≥ 1.4.0-beta.1&&< 1.4.0-beta.2 | 1.4.0-beta.2bundle update ember-source --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-0013 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2014-0013. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2014-0013 in your dependencies?
O3 Security finds CVE-2014-0013 across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.