dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-63024

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Order Delivery Date for WooCommerce order-delivery-date-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Order Delivery Date for WooCommerce: from n/a through <= 4.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 Order Delivery Date for WooCommerce plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to order delivery settings or data without proper privileges.

MitigationApply vendor patch when available and restrict user role permissions until the fix is deployed; audit existing user access levels in WooCommerce.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

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
    Navigate to WordPress admin > Plugins and verify Order Delivery Date for WooCommerce is installed and active
    Affected if plugin is installed and active in WordPress
  2. Identify installed plugin version
    In WordPress admin > Plugins, locate Order Delivery Date for WooCommerce and note the version number displayed
    Affected if installed version lacks the vendor security patch (compare against fixed version when published)
  3. Review user role capabilities
    Use a role management plugin or wp-admin > Users > Roles to examine which roles have access to Order Delivery Date settings (typically under WooCommerce > Order Delivery Date)
    Affected if roles without administrative privileges granted access to delivery settings or order data
  4. Inspect access control configuration
    Navigate to the plugin settings page (WooCommerce > Order Delivery Date > Settings) and check for authorization or role restriction options
    Affected if settings allow low-privilege users (subscriber, customer, or contributor) to modify delivery configurations
  5. Audit recent order access logs
    Check WordPress activity logs, WooCommerce logs, or server access logs for requests to plugin endpoints from unexpected user accounts
    Affected if non-administrator users accessed or modified delivery date settings without proper authorization

User is affected if the Order Delivery Date for WooCommerce plugin is installed AND unauthorized roles can access or modify delivery settings without administrator-level permissions.

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

Apply vendor patch when available and restrict user role permissions until the fix is deployed; audit existing user access levels in WooCommerce.

Recommended fix Moderate confidence

Version 4.3.2 or later (check official WordPress plugin repository for latest release)

  1. Check the WordPress plugin repository or the official Tyche Softwares website for the latest version of the Order Delivery Date for WooCommerce plugin
  2. Verify if version 4.3.2 or higher is available, as this would likely contain the security fix for the missing authorization vulnerability
  3. If a newer version exists, update the plugin through WordPress admin dashboard or via FTP/SFTP
  4. After updating, test that the order delivery date functionality continues to work correctly
  5. Ensure proper user role permissions are still configured as needed after the update
Caveat Review changelog for any breaking changes before updating, though minor version updates in WooCommerce plugins typically maintain backward compatibility

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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