dbcve.org
Ltl Freight QuotesWordPress extension · Eniture

CVE-2025-22289

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-16
Fix available
A fix is available. Upgrade to 2.5.9 or later.
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
Missing Authorization vulnerability in enituretechnology LTL Freight Quotes – Unishippers Edition ltl-freight-quotes-unishippers-edition allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LTL Freight Quotes – Unishippers Edition: from n/a through <= 2.5.8.

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

Missing authorization vulnerability in the enituretechnology LTL Freight Quotes Unishippers Edition WordPress plugin allows unauthenticated attackers to access sensitive functionality due to incorrectly configured access control security levels. The plugin fails to properly validate user permissions before executing certain actions, enabling unauthorized access to freight quote operations and potentially related administrative functions.

MitigationUpdate to the latest version of the plugin (beyond 2.5.8) which should include proper authorization checks, or conduct a code audit to identify all endpoints/functions lacking authorization and implement role-based access control checks before executing sensitive operations.

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:< 2.5.9

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
High
Availability
High

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

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 if the 'eniture-ltl-freight-quotes' or 'eniture-ltl-freight-quotes-unishippers' directory exists in your WordPress plugins folder (wp-content/plugins/)
    Affected if The plugin directory is present on the server
  2. Determine the installed version
    Open the main plugin file (usually named index.php or eniture-ltl-freight-quotes.php) and locate the version string in the plugin header comment, then compare it to the affected version range (anything below 2.5.9)
    Affected if The version number found is less than 2.5.9
  3. Identify accessible AJAX or REST endpoints
    Review the plugin files for registered AJAX actions (wp_ajax_*) or REST API routes (register_rest_route) that handle freight quote requests. These are typically found in the main plugin file or includes/*.php
    Affected if The plugin exposes quote-related endpoints without visible capability checks
  4. Test for unauthorized access
    If you have access to server logs or a security plugin, review access logs for requests to the plugin endpoints (such as wp-admin/admin-ajax.php?action=eniture_* or /wp-json/eniture/v1/*) originating from unauthenticated or low-privilege users
    Affected if Requests to plugin functionality succeed without authentication or without proper capability verification

If the Eniture LTL Freight Quotes plugin is installed and its version is below 2.5.9, the environment is vulnerable to unauthorized access due to missing authorization checks on the affected 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
Upgrade available Upgrade to 2.5.9 or later
Fixed in 2.5.9
Interim mitigation

Update to the latest version of the plugin (beyond 2.5.8) which should include proper authorization checks, or conduct a code audit to identify all endpoints/functions lacking authorization and implement role-based access control checks before executing sensitive operations.

Recommended fix High confidence

2.5.9

  1. 1. Create a complete backup of the WordPress site including database and files.
  2. 2. Navigate to the WordPress admin dashboard > Plugins section.
  3. 3. Locate 'LTL Freight Quotes – Unishippers Edition' (ltl-freight-quotes-unishippers-edition).
  4. 4. Click 'Update Now' to install version 2.5.9, or manually download version 2.5.9 from a trusted source and upload via Plugins > Add New > Upload Plugin.
  5. 5. After update completes, verify the plugin version shows 2.5.9 in the installed plugins list.
  6. 6. Test critical functionality (quote requests, admin settings access) to ensure the plugin operates correctly post-update.

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

Fix this in Ltl Freight Quotes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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