dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66071

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-21
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 tychesoftwares Custom Order Numbers for WooCommerce custom-order-numbers-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Custom Order Numbers for WooCommerce: from n/a through <= 1.11.0.

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 missing authorization vulnerability in the tychesoftwares Custom Order Numbers for WooCommerce plugin. The vulnerability allows attackers to exploit incorrectly configured access control security levels, likely enabling unauthorized access to administrative functions or manipulation of order numbers without proper capability checks.

MitigationImplement proper authorization and capability checks on all sensitive plugin functions and admin pages, and update to the latest patched version once 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
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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Custom Order Numbers for WooCommerce' by tychesoftwares. Note the installed version if visible.
    Affected if The plugin is installed and no version information or an unpatched version is shown
  2. Check plugin file headers for version
    Access the plugin directory via FTP or file manager: navigate to wp-content/plugins/orders-custom-numbers/ (or similar naming) and open the main PHP file to read the Version header in the plugin comment block.
    Affected if The version displayed is older than any patched version released by the vendor
  3. Identify exposed admin AJAX actions
    Check the plugin PHP files for wp_ajax_ and wp_ajax_nopriv_ hooks. Search for 'add_action("wp_ajax_' calls in the plugin directory and note which actions are registered without capability checks like current_user_can().
    Affected if AJAX actions are registered with wp_ajax_nopriv_ or lack current_user_can() validation
  4. Review REST API endpoint registration
    Search plugin files for 'register_rest_route' calls. Identify any endpoints that do not include permission_callback functions or permission checks restricting access to administrators.
    Affected if REST endpoints exist without proper permission_callback validation for admin-only access
  5. Test for unauthorized admin function access
    If you have access to the site codebase, examine the plugin for direct function calls or includes that execute sensitive order number manipulation without checking user capabilities (e.g., missing admin_init or manage_options checks).
    Affected if Sensitive order number functions can be accessed without administrator capability verification

A user is affected if the Custom Order Numbers for WooCommerce plugin is installed and exposes AJAX actions, REST endpoints, or admin functions that lack capability checks for authorization.

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 and capability checks on all sensitive plugin functions and admin pages, and update to the latest patched version once released.

Recommended fix Moderate confidence

Latest version of Custom Order Numbers for WooCommerce (version > 1.11.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Custom Order Numbers for WooCommerce' in the plugin list
  4. Check the current installed version (should be <= 1.11.0)
  5. Update the plugin to the latest available version via WordPress plugin updates, or download the latest version from wordpress.org/plugins and upload it
  6. After updating, verify the new version number reflects the update
  7. Test that WooCommerce order number functionality works correctly

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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