dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-13389

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-25
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 Admin and Customer Messages After Order for WooCommerce: OrderConvo plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the `get_order_by_id()` function in all versions up to, and including, 14. This makes it possible for unauthenticated attackers to view sensitive WooCommerce order details and private conversation messages between customers and store administrators for any order by supplying an arbitrary order ID.

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 OrderConvo plugin for WooCommerce has a broken access control vulnerability where the get_order_by_id() function lacks a capability check, allowing unauthenticated users to retrieve any order's details and private messages by simply supplying an order ID. This is an Insecure Direct Object Reference (IDOR) combined with missing authorization, exposing sensitive customer and order data.

MitigationUpdate the plugin to version 15 or later which should implement proper capability verification before allowing access to order data. If no update is available, consider disabling the plugin until a patched version is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify OrderConvo plugin is installed
    Navigate to WooCommerce > Plugins or check wp-content/plugins/ for the 'orderconvo' directory
    Affected if The OrderConvo plugin directory exists in the plugins folder
  2. Check installed OrderConvo version
    Look at the plugin main file header (e.g., orderconvo.php) or view the plugin details in WordPress admin plugins list
    Affected if The installed version is lower than version 15 (the fixed version)
  3. Confirm WooCommerce is active
    Verify WooCommerce is installed and active; this vulnerability only affects WooCommerce installations
    Affected if WooCommerce is running and the OrderConvo plugin is enabled
  4. Test unauthenticated order access
    Make a GET request to the plugin's REST endpoint (typically /wp-json/orderconvo/v1/orders/{id}) without providing authentication credentials
    Affected if The request returns order details or private messages without requiring login or capability verification

A user is affected if the OrderConvo plugin is installed with a version below 15 and the order retrieval endpoint is accessible without authentication.

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

Update the plugin to version 15 or later which should implement proper capability verification before allowing access to order data. If no update is available, consider disabling the plugin until a patched version is released.

Recommended fix Moderate confidence

Version 15 or later (latest available version from WordPress plugin repository)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Admin and Customer Messages After Order for WooCommerce: OrderConvo'
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, download the latest version from the WordPress plugin repository at plugins.trac.wordpress.org and upload it manually

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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