dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-27374

HIGH · 7.5 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 vanquish WooCommerce Order Details woocommerce-order-details allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WooCommerce Order Details: from n/a through <= 3.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

Missing authorization vulnerability in the vanquish WooCommerce Order Details plugin (woocommerce-order-details) allows unauthenticated or unauthorized attackers to bypass access control checks and view order details they should not have permission to access, due to incorrectly configured security levels.

MitigationImplement proper authorization checks at all access points for order data, verifying user permissions before returning any order information. The plugin version should be updated to the latest release if a patched version is available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the WooCommerce Order Details plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'WooCommerce Order Details' by vanquish or check the file path wp-content/plugins/woocommerce-order-details/ for existence
    Affected if The plugin folder 'woocommerce-order-details' exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Check the plugin header in wp-content/plugins/woocommerce-order-details/woocommerce-order-details.php for the 'Version' field, or view the plugin details in WordPress admin plugins list
    Affected if The version cannot be determined or is older than the latest patched release available from the vendor
  3. Verify WooCommerce is active
    Confirm WooCommerce is installed and active, as this plugin requires WooCommerce to function - check in Plugins > Installed Plugins for WooCommerce status
    Affected if WooCommerce is not active (the vulnerability only applies when WooCommerce and the plugin are both active)
  4. Inspect order detail access points for authorization checks
    Examine the plugin PHP files (particularly any files handling order-view or order-detail endpoints) for presence of current_user_can(), wp_verify_nonce(), or similar authorization validation before outputting order data
    Affected if The plugin code returns order information without verifying the current user owns or has permission to view the specific order ID being requested

The environment is affected if the WooCommerce Order Details plugin is installed and active, and the plugin code lacks proper authorization checks before exposing order data to users.

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

Implement proper authorization checks at all access points for order data, verifying user permissions before returning any order information. The plugin version should be updated to the latest release if a patched version is available.

Recommended fix Moderate confidence

Latest version of WooCommerce Order Details plugin (vendor should release a version newer than 3.1 with security fix)

  1. 1. Check the current version of the WooCommerce Order Details plugin (by vanquish) installed on your WordPress site.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate 'WooCommerce Order Details' (also may be listed as 'woocommerce-order-details') and note the current version.
  4. 4. Navigate to Plugins > Add New > Upload Plugin or directly download the latest version from the WordPress plugin repository.
  5. 5. Backup your WordPress database and files before performing the upgrade.
  6. 6. Deactivate the current version of the plugin.
  7. 7. Install and activate the latest available version of the WooCommerce Order Details plugin.
  8. 8. Verify that the authorization controls are functioning correctly after upgrade by testing access to order details with different user roles (especially non-privileged users).
Caveat Review plugin changelog for any breaking changes between version 3.1 and the latest version before upgrading, especially regarding order data access functionality

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

Have this fixed 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 help mitigating

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-2026-27374 — 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-27374 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