dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-54447

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
Saved search 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

This is a time-based blind SQL injection vulnerability in the saved search functionality of the affected application. An authenticated attacker can craft malicious input in the saved search feature that gets interpreted as SQL, allowing them to infer database contents by observing time delays in responses. This can lead to full database disclosure and potential account takeover if the database contains user credentials or session data.

MitigationImplement parameterized queries or prepared statements for all database interactions in the saved search functionality to prevent user input from being interpreted as SQL code. Validate and sanitize all user inputs before using them in database queries.

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. Identify if saved search feature exists
    Review application configuration and code for saved search functionality. Search for endpoints or functions that handle saved searches, such as 'saved search', 'search history', or 'custom search' features. Check the application's feature list or module documentation.
    Affected if The saved search functionality is present and accessible to authenticated users.
  2. Check application version against available patches
    Locate the application's version number in the administration panel, about page, or version file. Compare it to any vendor-released patch versions that address SQL injection fixes. If no version is exposed, skip to other checks.
    Affected if The installed version is older than the patched version containing the CVE fix.
  3. Inspect saved search database queries for parameterization
    Review source code or decompiled application files related to saved search functionality. Look for database query construction where user input from the saved search feature is concatenated or inserted directly into SQL strings without using parameterized queries, prepared statements, or ORM methods.
    Affected if User input from saved search fields is embedded directly into SQL queries without parameterized binding.
  4. Analyze database logs for time-based anomalies
    Enable and review database query logs, especially slow query logs. Monitor for repeated queries with similar patterns that exhibit unusual time delays, which may indicate time-based blind SQL injection testing.
    Affected if Database logs show queries from the saved search feature that produce inconsistent or unusually long response times correlated with user input patterns.
  5. Verify saved search input validation
    Examine input validation or sanitization code for saved search parameters. Check if there are whitelist filters, input length limits, or escaping mechanisms applied before the input reaches the database layer.
    Affected if No input validation, sanitization, or escaping is performed on saved search user inputs before database execution.
  6. Check database user privileges
    Review the database user credentials used by the application for saved search operations. Determine if the application database user has permissions beyond what is necessary, such as excessive table access or write capabilities.
    Affected if The application database user has more privileges than required, which could amplify the impact of successful SQL injection.

A user is affected if the saved search feature exists in their environment, the installed version is unpatched, and the feature processes user input without parameterized queries or input validation, enabling an authenticated attacker to inject time-delaying SQL commands.

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 interactions in the saved search functionality to prevent user input from being interpreted as SQL code. Validate and sanitize all user inputs before using them in database queries.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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