How severe is CVE-2012-6134?

CVE-2012-6134 has a CVSS 2.0 base score of 6.8, rated medium severity.

Is CVE-2012-6134 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (64th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2012-6134?

CVE-2012-6134 affects Omniauth-oauth2 Project Omniauth-oauth2. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2012-6134?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2012-6134 published?

CVE-2012-6134 was published on 2013-04-09 and last updated on 2026-06-16.

CVE-2012-6134

CVE-2012-6134 is a medium-severity vulnerability in Omniauth-oauth2 Project Omniauth-oauth2 with a CVSS 2.0 base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Severity: Medium (CVSS 2.0 base score 6.8)
EPSS exploit prediction: 1% (64th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-352
Affected product: Omniauth-oauth2 Project Omniauth-oauth2
Published: 2013-04-09
Last modified: 2026-06-16

Description

Cross-site request forgery (CSRF) vulnerability in the omniauth-oauth2 gem 1.1.1 and earlier for Ruby allows remote attackers to hijack the authentication of users for requests that modify session state.

Frequently asked questions

What is CVE-2012-6134?: Cross-site request forgery (CSRF) vulnerability in the omniauth-oauth2 gem 1.1.1 and earlier for Ruby allows remote attackers to hijack the authentication of users for requests that modify session state.
How severe is CVE-2012-6134?: CVE-2012-6134 has a CVSS 2.0 base score of 6.8, rated medium severity.
Is CVE-2012-6134 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (64th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-6134?: CVE-2012-6134 affects Omniauth-oauth2 Project Omniauth-oauth2. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2012-6134?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2012-6134 published?: CVE-2012-6134 was published on 2013-04-09 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:omniauth-oauth2_project:omniauth-oauth2:*:*:*:*:*:ruby:*:*

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

CVE-2025-32642 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in appsbd Vite Coupon vite-coupon allows Remote Code Inclusion.This…
CVE-2025-23922 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in Harsh iSpring Embedder embed-ispring allows Upload a Web Shell to a…
CVE-2017-5145 — Critical (CVSS 10.0): An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware…
CVE-2019-25729 — Critical (CVSS 9.8): PDF Signer 3.0 contains a server-side template injection vulnerability that allows unauthenticated attackers to execute…
CVE-2025-48340 — Critical (CVSS 9.8): Cross-Site Request Forgery (CSRF) vulnerability in Danny Vink User Profile Meta Manager user-profile-meta allows…
CVE-2025-2907 — Critical (CVSS 9.8): The Order Delivery Date WordPress plugin before 12.3.1 does not have authorization and CSRF checks when importing…

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →