How severe is CVE-2013-4492?

No CVSS score has been assigned to CVE-2013-4492 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-4492?

CVE-2013-4492 affects the following packages: i18n (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-4492?

Update i18n to 0.6.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4492 is resolved across your whole dependency graph.

How do I detect CVE-2013-4492 in my RubyGems dependencies?

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

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

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

CVE-2013-4492 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th 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-2013-4492?

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

CVE-2013-4492 was published on December 7, 2013 and was last updated on April 16, 2026. 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

CVE-2013-4492 — i18n

Fix: svenfuchs/i18n@92b57b1

CVE-2013-4492 is a Cross-site Scripting (XSS) vulnerability in i18n. A fix is available for i18n — see the affected versions and patch details below.

i18n gem Cross-site Scripting vulnerability

Also known asGHSA-r5hc-9xx5-97rw

Published

Dec 7, 2013

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

💎i18n

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

Cross-site scripting (XSS) vulnerability in exceptions.rb in the i18n gem before 0.6.6 for Ruby allows remote attackers to inject arbitrary web script or HTML via a crafted I18n::MissingTranslationData.new call.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`i18n`	all versions	0.6.6`bundle update i18n --conservative`

Affected Products

1 product · 1 configurations

Application

i18ni18n_project

≤ 0.6.5

range

Detection & mitigation playbook

Open-source dependency

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

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
CloudForms Management Engine 5.4	`cfme-0:5.4.0.5-1.el6cf`	RHBA-2015:1100
CloudForms Management Engine 5.7	`cfme-0:5.7.1.3-1.el7cf`	RHSA-2017:0320
CloudForms Management Engine 5.9	`ansible-0:2.4.3.0-1.el7ae`	RHSA-2018:0380

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-4492 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works