How severe is CVE-2013-0233?

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

Which packages are affected by CVE-2013-0233?

CVE-2013-0233 affects the following packages: devise (RubyGems), devise (RubyGems), devise (RubyGems), devise (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-0233?

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

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

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

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

Yes. There are 3 known exploit references for CVE-2013-0233, including 3 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-2013-0233?

CVE-2013-0233 has an EPSS (Exploit Prediction Scoring System) score of 14.1%, placing it in the 97th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2013-0233?

CVE-2013-0233 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2013-0233 was published on April 25, 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-2013-0233 — devise

CVE-2013-0233 is a CWE-399 vulnerability in devise. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for devise — see the affected versions and patch details below.

Devise does not properly perform type conversion when performing database queries

Also known asGHSA-jxhw-mg8m-2pj8

Published

Apr 25, 2013

Updated

Apr 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

14.1%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

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

Real-World Exposure

4 pkgs affected

💎devise💎devise💎devise💎devise

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

Devise gem 2.2.x before 2.2.3, 2.1.x before 2.1.3, 2.0.x before 2.0.5, and 1.5.x before 1.5.4 for Ruby, when using certain databases, does not properly perform type conversion when performing database queries, which might allow remote attackers to cause incorrect results to be returned and bypass security checks via unknown vectors, as demonstrated by resetting passwords of arbitrary accounts.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`devise`	≥ 2.2.0&&< 2.2.3	2.2.3`bundle update devise --conservative`
💎RubyGems	`devise`	≥ 2.1.0&&< 2.1.3	2.1.3`bundle update devise --conservative`
💎RubyGems	`devise`	≥ 2.0.0&&< 2.0.5	2.0.5`bundle update devise --conservative`
💎RubyGems	`devise`	≥ 1.5.0&&< 1.5.4	1.5.4`bundle update devise --conservative`

Affected Products

2 products · 16 configurations

opensuseopensuse

1 version

12.2

Application

deviseplataformatec

15 versions

1.5.01.5.11.5.21.5.32.0.02.0.12.0.22.0.32.0.42.1.02.1.12.1.2

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.

Devise gem 2.2.x before 2.2.3, 2.1.x before 2.1.3, 2.0.x before 2.0.5, a…

metasploit.comNVDOct 2018

Report on phenoelit.org

phenoelit.orgNVDOct 2018

Report on github.com

github.comMetasploitOct 2020

Detection & mitigation playbook

Open-source dependency

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

O3 Security · Impact-Aware SCA

Is CVE-2013-0233 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works