Ltl Freight QuotesWordPress extension · Eniture

CVE-2024-13473

HIGH · 7.5 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 5.0.21 or later.
See remediation →
84/100
Remediation priority · High
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
The LTL Freight Quotes – Worldwide Express Edition plugin for WordPress is vulnerable to SQL Injection via the 'dropship_edit_id' and 'edit_id' parameter in all versions up to, and including, 5.0.20 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 LTL Freight Quotes WordPress plugin fails to properly sanitize user input in the 'dropship_edit_id' and 'edit_id' parameters, allowing unauthenticated attackers to inject arbitrary SQL commands into existing queries. This occurs due to insufficient input escaping and missing prepared statements in the SQL queries.

MitigationUpdate the plugin to a version newer than 5.0.20, or implement proper input validation and convert all SQL queries to use prepared statements with parameterized queries.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ltl Freight QuotesWordPress extension
Affected:< 5.0.21

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Verify the Eniture LTL Freight Quotes plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Eniture Ltl Freight Quotes' or 'LTL Freight Quotes' in the list of installed plugins.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In the Plugins list, locate the Eniture LTL Freight Quotes plugin and note the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the Version field.
    Affected if The installed version is lower than 5.0.21 (for example, 5.0.20, 5.0.19, etc.)
  3. Confirm the vulnerable parameters are accessible
    Review the WordPress site's public-facing pages or admin pages that handle 'dropship_edit_id' or 'edit_id' parameters, such as forms, admin panels, or AJAX handlers that use these parameters in requests.
    Affected if The plugin handles requests containing 'dropship_edit_id' or 'edit_id' parameters without proper input validation

The environment is affected if the Eniture LTL Freight Quotes plugin is installed with a version lower than 5.0.21 and the site processes requests using the vulnerable 'dropship_edit_id' or 'edit_id' parameters.

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
Upgrade available Upgrade to 5.0.21 or later
Fixed in 5.0.21
Interim mitigation

Update the plugin to a version newer than 5.0.20, or implement proper input validation and convert all SQL queries to use prepared statements with parameterized queries.

Recommended fix High confidence

5.0.21

  1. 1. Back up your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Find the 'LTL Freight Quotes – Worldwide Express Edition' plugin.
  4. 4. If automatic updates are enabled, the plugin should update to version 5.0.21 automatically. If not, click 'Update Now' to update to the latest version.
  5. 5. Verify the plugin updated successfully by checking the version number in the plugins list.
  6. 6. Confirm the fix by ensuring the 'dropship_edit_id' and 'edit_id' parameters are now properly sanitized and the SQL queries use prepared statements.

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

Fix this in Ltl Freight Quotes Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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