dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3646

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 – R+L Carriers Edition plugin for WordPress is vulnerable to Missing Authorization via the plugin's webhook handler in all versions up to, and including, 3.3.13. This is due to missing authentication, authorization, and nonce verification on a standalone PHP file that directly processes GET parameters and updates WordPress options. This makes it possible for unauthenticated attackers to modify the plugin's subscription plan settings, effectively downgrading the store from a paid plan to the Trial Plan, changing the store type, and manipulating subscription expiration dates, potentially disabling premium features such as Dropship and Hazardous Material handling.

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 – R+L Carriers Edition WordPress plugin contains a standalone PHP file that lacks authentication, authorization, and nonce verification checks. This allows unauthenticated attackers to submit GET requests directly to this file and modify WordPress options, downgrading subscription plans from paid to Trial, altering store type settings, and manipulating expiration dates to disable premium features.

MitigationUpdate the plugin to version 3.3.14 or later once released; until then, disable or remove the vulnerable standalone PHP file and consider restricting access via web server rules.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Confirm plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'LTL Freight Quotes - R+L Carriers Edition'. Check the version number displayed. Alternatively, inspect the plugin main PHP file header for the 'Version' tag.
    Affected if The installed version is below 3.3.14 (or if the version cannot be determined and the plugin is present).
  2. Locate the webhook handler file
    Search the wp-content/plugins directory for the plugin folder (likely named 'rl-carriers-ltl-freight-quotes' or similar). Look for PHP files that handle webhooks, callbacks, or external requests, particularly any standalone PHP files outside the main plugin structure.
    Affected if A standalone webhook handler PHP file exists in the plugin directory.
  3. Check file accessibility
    Attempt to access the identified webhook handler file directly via browser or curl (e.g., GET request to the file URL). Observe whether the server returns a response rather than a 404 or redirect.
    Affected if The webhook file is directly accessible via web browser without authentication.
  4. Verify lack of authorization checks
    Open the webhook handler PHP file in a text editor or via file manager. Search for function calls that update WordPress options (update_option, add_option, wp_cache_set related to options) and check if they are preceded by authentication checks (is_user_logged_in, current_user_can, wp_verify_nonce) or capability checks.
    Affected if The code updates WordPress options without any authentication, authorization, or nonce verification before the update_option calls.
  5. Test option modification vulnerability
    Send a crafted GET request to the webhook endpoint with parameters that would modify options (such as ?plan=trial or ?store_type=retail). Check if the WordPress options are actually changed by reading them afterward via admin or database query.
    Affected if Unauthenticated requests successfully modify plugin settings or subscription options in the WordPress options table.

Your environment is affected if the LTL Freight Quotes plugin is installed with a version prior to 3.3.14 and contains a standalone webhook handler file that allows unauthenticated modification of WordPress options.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 3.3.14 or later once released; until then, disable or remove the vulnerable standalone PHP file and consider restricting access via web server rules.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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