dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14843

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-24
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 Wizit Gateway for WooCommerce plugin for WordPress is vulnerable to Unauthenticated Arbitrary Order Cancellation in all versions up to, and including, 1.3.1. This is due to a lack of authentication and authorization checks in the 'handle_checkout_redirecturl_response' function. This makes it possible for unauthenticated attackers to cancel arbitrary WooCommerce orders by sending a crafted request with a valid 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 Wizit Gateway for WooCommerce plugin for WordPress is vulnerable to an Insecure Direct Object Reference (IDOR) flaw in the 'handle_checkout_redirecturl_response' function. This function processes checkout redirect responses but fails to verify that the requesting user owns or has authorization to modify the specified order. An unauthenticated attacker can cancel arbitrary WooCommerce orders by sending a crafted request containing a valid order ID.

MitigationUpdate to the latest version of the Wizit Gateway for WooCommerce plugin (beyond 1.2.9) when available, or disable the plugin until a patch is released. If no patch is available, implement a webhook signature validation or token-based authorization mechanism server-side to verify the requester owns the order.

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. Confirm Wizit Gateway plugin is installed
    Check the WordPress plugins directory for the Wizit Gateway for WooCommerce plugin folder and main plugin file
    Affected if Plugin folder exists in /wp-content/plugins/ containing wizit-gateway files
  2. Identify installed plugin version
    Open the main plugin PHP file and locate the Version header in the plugin comment block, or query the WordPress database wp_options table for the active_plugins option
    Affected if Version is 1.2.9 or lower (versions through 1.2.9 are affected)
  3. Verify WooCommerce is active
    Check if WooCommerce plugin is active by examining wp_options table for 'active_plugins' option or checking for WooCommerce classes/functions on the site
    Affected if WooCommerce is installed and active (required for the vulnerable function to process orders)
  4. Identify the vulnerable callback endpoint
    Search plugin code for 'handle_checkout_redirecturl_response' function and examine what hook or action it is attached to (typically a WordPress init or wp_ajax hook)
    Affected if The function exists and is hooked to an unauthenticated-accessible action (no capability check or nonce verification present)
  5. Inspect authorization logic in the vulnerable function
    Review the handle_checkout_redirecturl_response function code to confirm it lacks order ownership verification (no check that current user matches order customer)
    Affected if Function processes order cancellation without verifying requester owns or is authorized to modify the order

User is affected if the Wizit Gateway for WooCommerce plugin version is 1.2.9 or lower, WooCommerce is active, and the plugin lacks proper order ownership validation in the checkout redirect handler.

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

Update to the latest version of the Wizit Gateway for WooCommerce plugin (beyond 1.2.9) when available, or disable the plugin until a patch is released. If no patch is available, implement a webhook signature validation or token-based authorization mechanism server-side to verify the requester owns the order.

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