dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-12245

HIGH · 8.7 CVSS v4.0 Published 2025-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Logout functionality contains a blind SQL injection that can be exploited by unauthenticated attackers. Using a time-based blind SQLi technique the attacker can disclose all database contents. Account takeover is a potential outcome depending on the presence or lack thereof entries in certain database tables.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The logout functionality in this application contains a time-based blind SQL injection vulnerability that can be exploited by unauthenticated attackers. By injecting malicious SQL queries through the logout endpoint, attackers can infer database contents through time delays, potentially extracting sensitive data and achieving account takeover depending on database schema.

MitigationReplace dynamic SQL queries in the logout function with parameterized queries or prepared statements, and implement proper input validation to sanitize all user-supplied data before database interactions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify logout endpoint accessibility
    Determine if the logout endpoint (commonly /logout, /logoff, /signout, or similar) is accessible without authentication by examining the application's authentication configuration and testing the endpoint directly.
    Affected if The logout endpoint is publicly accessible without requiring authentication.
  2. Locate logout function code
    Search the application source code for the logout handler/function - look for files containing 'logout', 'logoff', or 'signout' in function names, and examine the database query logic within these functions.
    Affected if The logout functionality contains direct database queries that handle user session or session data.
  3. Check for dynamic SQL usage in logout
    Examine the logout function code for dynamic SQL construction - look for string concatenation, string formatting, or raw query building where user input or session identifiers are directly inserted into SQL queries without using parameterized queries or prepared statements.
    Affected if The logout function constructs SQL queries dynamically using string concatenation or formatting with user-controlled input.
  4. Verify if session data is used in queries
    Review the logout function to identify if session identifiers, cookies, or other user-supplied data are passed directly to database queries within the logout process.
    Affected if Session tokens, cookies, or other user-supplied data are directly included in SQL queries within the logout function without proper sanitization or parameterization.
  5. Test for time-based injection response
    Send crafted requests to the logout endpoint with SQL injection payloads designed to cause time delays (e.g., using SLEEP(), WAITFOR DELAY, or pg_sleep functions) and measure response times to confirm time-based behavior.
    Affected if The application exhibits delayed responses corresponding to injected time-delay SQL commands, confirming the injection point is vulnerable.

If the logout endpoint is accessible without authentication and the logout function uses dynamic SQL with user-supplied input without parameterization, the environment is likely affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries in the logout function with parameterized queries or prepared statements, and implement proper input validation to sanitize all user-supplied data before database interactions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12245 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data