dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-54445

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
Login 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

This is a time-based blind SQL injection vulnerability in the login functionality that allows unauthenticated attackers to inject malicious SQL queries through login input fields. Attackers can infer database content by observing time delays in responses, potentially enabling full database disclosure and account takeover.

MitigationImmediate remediation requires replacing dynamic SQL queries with parameterized queries/prepared statements, implementing strict input validation on all login fields, and conducting thorough penetration testing to verify the fix.

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 the affected application and version
    Locate the application name, version number, and build information from the application's about page, header metadata, or installation directory documentation. Compare this version against any official vulnerability advisories or release notes for CVE-2024-54445.
    Affected if The installed application version matches a version known to be affected by this CVE or no version information is available but the login behavior matches the vulnerability description.
  2. Locate the login functionality
    Identify all endpoints or interfaces that handle user authentication, including web login forms, API login endpoints, mobile app login, and any SSO integration points. Document the URL paths and HTTP methods used.
    Affected if The application has a login function that processes user-supplied credentials.
  3. Verify input handling in login parameters
    Inspect the login request by submitting test credentials with special SQL characters (such as single quotes, semicolons, or comment syntax) in the username and password fields. Observe whether the application returns database error messages or behaves unexpectedly.
    Affected if The login function reflects submitted input in error messages, displays unusual behavior, or fails to sanitize special characters in username/password fields.
  4. Test for time-based blind SQL injection
    Submit login credentials containing time-delay SQL functions (such as SLEEP(5), WAITFOR DELAY '00:00:05', or pg_sleep(5)) in the username or password field. Measure the response time difference between normal requests and requests containing the delay payload.
    Affected if The application response is delayed by approximately the specified time period (e.g., 5+ seconds) when a time-delay payload is submitted, indicating successful SQL injection execution.
  5. Check for SQL injection mitigations
    Review application source code, configuration files, or API documentation to determine whether the login functionality uses parameterized queries, prepared statements, or input validation/sanitization for all SQL interactions involving user input.
    Affected if The login code uses dynamic SQL concatenation without parameterized queries, or no documentation confirms the use of secure query handling.

If the application has a login function that processes user input without parameterized queries and exhibits delayed responses to time-delay SQL payloads, the environment is affected by CVE-2024-54445.

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

Immediate remediation requires replacing dynamic SQL queries with parameterized queries/prepared statements, implementing strict input validation on all login fields, and conducting thorough penetration testing to verify the fix.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54445 — 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-54445 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