dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-54446

HIGH · 7.1 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 →
77/100
Remediation priority · High
Remotely reachable 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
Document history functionality contains a blind SQL injection that can be exploited by authenticated 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

A time-based blind SQL injection vulnerability exists in the document history functionality. Authenticated attackers can manipulate SQL queries through unsanitized input to extract database contents using time-delay techniques, potentially achieving account takeover by accessing user credential tables.

MitigationImplement parameterized queries or prepared statements for all database operations in the document history feature, combined with strict input validation and principle of least privilege on database accounts.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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. Locate document history feature
    Identify the code module, API endpoint, or component that handles document history (search for terms like document_history, version_history, audit_log, or document_audit in your codebase). Determine where user-supplied input (document IDs, timestamps, user IDs) is processed.
    Affected if The document history feature exists and accepts user input that reaches the database layer without proper sanitization
  2. Verify authentication is required
    Review access controls on the document history endpoint. Check that unauthenticated requests are properly rejected and that session validation occurs before any database query is executed.
    Affected if The document history endpoint can be accessed without valid authentication or session validation is missing
  3. Review SQL query construction
    Examine the code that builds SQL queries for document history. Look for dynamic SQL construction using string concatenation, formatting functions, or string interpolation with user-supplied parameters. Search for use of parameterized queries (prepared statements) versus direct query building.
    Affected if User input is concatenated directly into SQL query strings rather than bound as parameters
  4. Check input validation on history parameters
    Inspect how input parameters (document IDs, date ranges, user identifiers) are validated before being used in database queries. Look for type checking, length limits, and allowlist validation.
    Affected if Input validation is absent, weak, or can be bypassed for SQL injection payloads
  5. Assess database account privileges
    Examine the database user account that the application uses for document history queries. Check what tables and operations it has access to, particularly user credential or password tables.
    Affected if The application database account has unnecessary privileges enabling access to sensitive credential tables

You are affected if the document history feature exists and processes user input through direct SQL string concatenation instead of parameterized queries, allowing time-based blind SQL injection for data extraction.

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

Implement parameterized queries or prepared statements for all database operations in the document history feature, combined with strict input validation and principle of least privilege on database accounts.

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-54446 — 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-54446 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