dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22290

CRITICAL · 9.3 CVSS v3.1 Published 2025-02-16
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 – FreightQuote Edition ltl-freight-quotes-freightquote-edition allows SQL Injection.This issue affects LTL Freight Quotes – FreightQuote Edition: from n/a through <= 2.3.11.

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 – FreightQuote Edition WordPress plugin. The plugin fails to properly neutralize special elements in SQL commands, allowing authenticated or unauthenticated attackers to inject malicious SQL queries. Successful exploitation could allow attackers to read, modify, or delete database contents.

MitigationUpdate to the latest version of the plugin as soon as a vendor patch is released. If no patch is available, disable the plugin or implement input validation/sanitization on all database queries as a temporary workaround.

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. Verify the plugin is installed
    Check the WordPress plugins directory or use wp-cli: wp plugin list --name='enituretechnology-ltl-freight-quotes' or inspect /wp-content/plugins/ for a folder starting with 'enituretechnology'
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed version
    Check the plugin's main PHP file for the Version header in the plugin comment block, or use wp-cli: wp plugin get <plugin-folder-name> --field=version
    Affected if The installed version is lower than the patched version released by the vendor
  3. Determine if the plugin is active
    Check WordPress admin/plugins.php or use wp-cli: wp plugin status <plugin-folder-name>
    Affected if The plugin shows as 'Active' and the vulnerable code is reachable
  4. Review access controls
    Check if the plugin's AJAX endpoints or public-facing forms are accessible to unauthenticated users by inspecting the plugin's PHP code for 'add_action' hooks on 'wp_ajax' or 'wp_ajax_nopriv'
    Affected if The plugin registers hooks accessible to unauthenticated users (wp_ajax_nopriv) without additional authorization checks
  5. Inspect SQL query handling
    Examine the plugin's PHP files for direct $wpdb queries, especially those using $_POST, $_GET, or $_REQUEST variables without proper sanitization using $wpdb->prepare()
    Affected if Code contains unsanitized input passed directly to SQL queries (e.g., $wpdb->query($_REQUEST['parameter']) without prepare())

A user is affected if the enituretechnology LTL Freight Quotes plugin is installed, active, and running a version lacking the SQL injection fix with unauthenticated access to vulnerable query endpoints.

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

Update to the latest version of the plugin as soon as a vendor patch is released. If no patch is available, disable the plugin or implement input validation/sanitization on all database queries as a temporary workaround.

Recommended fix Moderate confidence

Upgrade to the latest version of LTL Freight Quotes – FreightQuote Edition available from enituretechnology (version 2.3.12 or later if released)

  1. 1. Check the WordPress admin panel for the plugin 'LTL Freight Quotes – FreightQuote Edition' and note the current installed version.
  2. 2. Navigate to the WordPress plugin repository or the official enituretechnology website to identify the latest available version of the plugin.
  3. 3. Before upgrading, backup the entire WordPress site including the database to ensure data safety.
  4. 4. Upgrade the plugin to the latest version available from the official source.
  5. 5. Verify the upgrade was successful by checking the installed version number.
  6. 6. Test critical functionality of the plugin (quote requests, freight calculations) to ensure the upgrade did not break existing features.
  7. 7. Review the site logs for any SQL injection attempts that may have occurred prior to patching.
Caveat Review plugin changelog for any breaking changes between current version and latest version before upgrading

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
  • 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-2025-22290 — 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-22290 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