How severe is CVE-2013-4562?

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

Which packages are affected by CVE-2013-4562?

CVE-2013-4562 affects the following packages: omniauth-facebook (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-4562?

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

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

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

How do I mitigate CVE-2013-4562 if there is no patch (or I can't update yet)?

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.

Is CVE-2013-4562 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-4562, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-4562?

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

CVE-2013-4562 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-4562 published, and has it been updated?

CVE-2013-4562 was published on October 24, 2017 and was last updated on November 30, 2024. 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-4562 — omniauth-facebook

Fix: mkdynamic/omniauth-facebook@ccfcc26

CVE-2013-4562 is a Cross-Site Request Forgery (CSRF) vulnerability in omniauth-facebook. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for omniauth-facebook — see the affected versions and patch details below.

omniauth-facebook Cross-Site Request Forgery vulnerability

Published

Oct 24, 2017

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

💎omniauth-facebook

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

The omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the session parameter, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via the state parameter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`omniauth-facebook`	≥ 1.4.1&&< 1.5.0	1.5.0`bundle update omniauth-facebook --conservative`

Affected Products

1 product · 1 configurations

Application

omniauth-facebookmadeofcode

1 version

1.4.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the…

github.comNVDMay 2014

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

The omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the session parameter, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via the state parameter.

O3 Security · Impact-Aware SCA

Is CVE-2013-4562 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works