dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39672

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
Missing Authorization vulnerability in shiptime ShipTime: Discounted Shipping Rates shiptime-discount-shipping allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ShipTime: Discounted Shipping Rates: from n/a through <= 1.1.1.

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

The ShipTime: Discounted Shipping Rates WordPress plugin (shiptime-discount-shipping) versions up to 1.1.1 contains a missing authorization vulnerability allowing unauthenticated or unauthorized users to access functionality that should be restricted. The plugin incorrectly implements access control checks, permitting actions that should require proper authorization verification.

MitigationImplement proper WordPress capability checks and nonce verification on all AJAX endpoints and admin pages within the plugin to ensure only authorized users can access shipping rate configuration and discount settings.

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. Verify ShipTime plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ShipTime: Discounted Shipping Rates' (shiptime-discount-shipping). Note the version number displayed. Alternatively, check the main plugin file (wp-content/plugins/shiptime-discount-shipping/shiptime-discount-shipping.php) for the 'Version' header in the plugin comment block.
    Affected if Version is 1.1.1 or lower (the vulnerability affects versions through 1.1.1)
  2. Inspect plugin AJAX endpoints for capability checks
    Examine the main plugin PHP file and any included files for add_action calls registering AJAX handlers (like 'wp_ajax_shiptime_*'). For each AJAX endpoint, locate the callback function and verify it includes current_user_can() or a similar capability check before executing sensitive operations.
    Affected if AJAX endpoints exist that process shipping rate data or administrative actions WITHOUT current_user_can() or similar authorization checks
  3. Review admin function access controls
    Search the plugin files for functions that perform administrative or sensitive operations (e.g., updating settings, retrieving shipping rates, modifying data). Identify if these functions check user capabilities (such as 'manage_options' or 'edit_posts') before executing.
    Affected if Admin or sensitive functions lack capability verification and can be called by any authenticated user or unauthenticated requester
  4. Check nonce verification on sensitive actions
    Locate all form submissions and AJAX requests in the plugin that modify data or retrieve sensitive information. Verify each includes wp_verify_nonce() or check_admin_referer() before processing the request.
    Affected if Sensitive actions process requests without nonce verification, allowing potential CSRF exploitation

Your environment is affected if the ShipTime plugin version is 1.1.1 or lower AND the plugin exposes AJAX endpoints or admin functions that lack proper capability checks and nonce 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.

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

Implement proper WordPress capability checks and nonce verification on all AJAX endpoints and admin pages within the plugin to ensure only authorized users can access shipping rate configuration and discount settings.

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-39672 — 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-39672 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