CVE-2013-4562: The omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the session parameter, which allows remot
CVE-2013-4562 is a medium-severity flaw (CVSS 6.8) affecting omniauth-facebook. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 6.8 (Medium) |
| EPSS exploit chance | 1.2% (top 33%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2014-05-13 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2013-4562?
omniauth-facebook: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2013-4562 being exploited?
CVE-2013-4562 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2013-4562 affect?
CVE-2013-4562 affects omniauth-facebook. Severity is medium (CVSS 6.8). 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.
How urgent is CVE-2013-4562?
Priority 46/100. Public exploit reference
Related CVEs
- CVE-2013-4593 HIGH 7.5 UPGRADE RubyGem omniauth-facebook has an access token security vulnerability