dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-22287

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in enituretechnology LTL Freight Quotes – FreightQuote Edition ltl-freight-quotes-freightquote-edition allows Exploiting Incorrectly Configured Access Control Security Levels.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

This is a WordPress plugin for LTL freight quote integration that contains a missing authorization vulnerability, allowing attackers to access functionality they shouldn't have permission to use due to incorrectly configured access control security levels.

MitigationApply vendor patch when available (version > 2.3.11). Until then, implement compensating controls such as API authentication requirements, IP allowlisting, or web application firewall rules to restrict access to sensitive endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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. Identify the LTL freight quote plugin and its version
    In WordPress admin, go to Plugins > Installed Plugins and locate the LTL freight quote plugin. Note its version number from the plugin details. Alternatively, check the plugin's main PHP file for the Version header comment.
    Affected if The installed version is 2.3.11 or lower, or if the version cannot be determined but the plugin is present
  2. Verify WordPress REST API accessibility to plugin endpoints
    Use a tool like curl or Burp Suite to send unauthenticated GET/POST requests to common WordPress plugin REST API routes, such as /wp-json/ltl/v1/ or similar freight-quote-related endpoints. Inspect the HTTP response code and content.
    Affected if The server returns 200 OK with sensitive data (quotes, pricing, customer info) instead of 401 Unauthorized or 403 Forbidden for unauthenticated requests
  3. Test admin AJAX actions without authentication
    Send a POST request to /wp-admin/admin-ajax.php with plugin-related action parameters (such as action=get_quote or action=fetch_freight_rates) without providing any authentication cookies or nonces. Check if the action executes successfully.
    Affected if The response indicates successful execution or returns data that should require admin privileges, rather than returning an error or requiring authentication
  4. Inspect user role and capability requirements in plugin code
    If direct code access is available, examine the plugin's PHP files for capability checks (current_user_can, add_cap, roles) around sensitive functions like quote generation, rate fetching, or customer data retrieval. Compare the required capability level against the actual sensitivity of the function.
    Affected if No capability check is found before sensitive operations, or the check uses a low-privilege capability (like 'read') for operations that should require 'manage_options' or 'edit_posts'

You are affected if the LTL freight quote plugin is installed at version 2.3.11 or lower AND any of its sensitive endpoints or AJAX actions are accessible without authentication or proper capability verification.

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

Apply vendor patch when available (version > 2.3.11). Until then, implement compensating controls such as API authentication requirements, IP allowlisting, or web application firewall rules to restrict access to sensitive endpoints.

Recommended fix Moderate confidence

Latest available version (newer than 2.3.11)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate "LTL Freight Quotes – FreightQuote Edition" by enituretechnology
  4. If an update is available, click "Update Now" to install the latest version
  5. Verify the update completes successfully
  6. Test that the plugin functionality works as expected after the update

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 / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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