How severe is CVE-2012-6497?

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

Which packages are affected by CVE-2012-6497?

CVE-2012-6497 affects the following packages: authlogic (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2012-6497?

Update authlogic to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-6497 is resolved across your whole dependency graph.

How do I detect CVE-2012-6497 in my RubyGems dependencies?

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

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

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2012-6497 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2012-6497, including 2 in-the-wild exploitations 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-2012-6497?

CVE-2012-6497 has an EPSS (Exploit Prediction Scoring System) score of 2.7%, placing it in the 86th 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-2012-6497?

CVE-2012-6497 is classified as SQL Injection (CWE-89). 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-2012-6497 published, and has it been updated?

CVE-2012-6497 was published on January 4, 2013 and was last updated on April 10, 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-2012-6497 — authlogic

Fix: binarylogic/authlogic#341

CVE-2012-6497 is a SQL Injection vulnerability in authlogic. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for authlogic — see the affected versions and patch details below.

Authlogic Information Exposure vulnerability

Also known asGHSA-rx7j-mw4c-76g9

Published

Jan 4, 2013

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

💎authlogic

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 Authlogic gem for Ruby on Rails, when used with certain versions before 3.2.10, makes potentially unsafe find_by_id method calls, which might allow remote attackers to conduct CVE-2012-6496 SQL injection attacks via a crafted parameter in environments that have a known secret_token value, as demonstrated by a value contained in secret_token.rb in an open-source product.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`authlogic`	all versions	3.3.0`bundle update authlogic --conservative`

Affected Products

1 product · 1 configurations

Application

railsrubyonrails

< 3.2.10

range

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 Authlogic gem for Ruby on Rails, when used with certain versions bef…

phenoelit.orgNVDAug 2019

Report on blog.phusion.nl

blog.phusion.nlNVDAug 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for authlogic, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update authlogic to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-6497 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-6497 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works