dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-24664

CRITICAL · 9.3 CVSS v3.1 Published 2025-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in enituretechnology LTL Freight Quotes – Worldwide Express Edition ltl-freight-quotes-worldwide-express-edition allows SQL Injection.This issue affects LTL Freight Quotes – Worldwide Express Edition: from n/a through <= 5.0.20.

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 · moderate confidence

A SQL Injection vulnerability exists in the enituretechnology LTL Freight Quotes – Worldwide Express Edition WordPress plugin (versions up to 5.0.20). The vulnerability stems from improper neutralization of special elements in SQL commands, allowing attackers to inject malicious SQL queries through unsanitized input parameters.

MitigationUpgrade to version 5.0.21 or later. If upgrade is not immediately possible, implement input validation and parameterized queries on all database interactions as an interim measure.

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
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

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 the plugin installation directory
    Check the WordPress plugins folder at wp-content/plugins/ for a directory named 'ltl-freight-quotes-worldwide-express' or similar enituretechnology LTL freight plugin directories.
    Affected if The plugin directory exists in the WordPress installation.
  2. Retrieve the installed plugin version
    Open the main plugin PHP file (usually the one with the same name as the directory) and locate the plugin header comment containing 'Version:' to identify the currently installed version.
    Affected if The version number displayed is 5.0.20 or lower.
  3. Confirm WordPress core version
    Check WordPress version in Dashboard > At a Glance or by inspecting wp-includes/version.php.
    Affected if Any WordPress version is running with the vulnerable plugin version.
  4. Verify plugin is active
    Check the WordPress database table wp_options for option_name containing 'active_plugins' and verify the plugin is listed among active plugins.
    Affected if The plugin appears in the list of active plugins.

You are affected if the enituretechnology LTL Freight Quotes - Worldwide Express Edition plugin is installed, active, and running version 5.0.20 or lower.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 5.0.21 or later. If upgrade is not immediately possible, implement input validation and parameterized queries on all database interactions as an interim measure.

Recommended fix Moderate confidence

Upgrade to the latest available version of LTL Freight Quotes – Worldwide Express Edition (version 5.0.21 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'LTL Freight Quotes – Worldwide Express Edition' by enituretechnology
  4. Check the current version displayed (should be 5.0.20 or earlier)
  5. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository
  6. After updating, verify the plugin version is newer than 5.0.20
  7. Test the plugin functionality to ensure the update does not break existing features

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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