CVE-2026-103361

Payment Gateway via Valitor for WooCommerce < 1.9.41 - Unauthenticated Payment Bypass via a Shipped Default Verification Code

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
The Payment Gateway via Valitor for WooCommerce WordPress plugin before 1.9.41 does not properly validate the authenticity of payment callbacks, relying on a verification secret that ships with a hard-coded default value used by every store that has not changed it, allowing unauthenticated attackers to forge a valid payment confirmation and mark arbitrary orders as paid.

Analysis

AI-generated

Technical impact

The Payment Gateway via Valitor for WooCommerce plugin allows an attacker to craft a payment callback that the system accepts as authentic because it relies on a hard‑coded verification secret shipped with every installation. By forging a callback containing a valid but default secret, an unauthenticated attacker can cause arbitrary orders to be marked as paid, enabling financial fraud and eroding the integrity of the store’s revenue tracking. This flaw represents an authentication bypass allowing the attacker to alter order status without possessing legitimate payment confirmation.

Affected Systems

Any WordPress site that has installed the Payment Gateway via Valitor for WooCommerce plugin at a version prior to 1.9.41 and has not changed the default verification code is affected. The plugin itself is offered by an undisclosed vendor and is distributed as part of the WordPress ecosystem through the plugin repository.

Risk and Exploitability

Exploit knowledge is sufficient for a remote attacker to execute the attack by sending a malicious callback to the plugin’s payment confirmation endpoint. While the exploit simply requires HTTP access to that endpoint, the attacker can target any system with the vulnerable plugin regardless of user authentication. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, yet the potential financial damage and ease of exploitation suggest a high risk. The lack of official mitigation details from the vendor underscores the urgency of patching or manually hardening the verification process.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the plugin to version 1.9.41 or later where the hard‑coded verification secret is removed.
  • If an upgrade is not possible, immediately replace the default verification secret with a unique, strong value and configure the plugin to require this secret for all callbacks.
  • Disable automatic order completion or enforce manual confirmation of orders until an authenticated verification process is in place.

Generated by OpenCVE AI on November 15, 2026 at 07:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-284
CWE-798
Type Values Removed Values Added
Description The Payment Gateway via Valitor for WooCommerce WordPress plugin before 1.9.41 does not properly validate the authenticity of payment callbacks, relying on a verification secret that ships with a hard-coded default value used by every store that has not changed it, allowing unauthenticated attackers to forge a valid payment confirmation and mark arbitrary orders as paid.
Title Payment Gateway via Valitor for WooCommerce < 1.9.41 - Unauthenticated Payment Bypass via a Shipped Default Verification Code
References

Subscriptions

No data.

Weaknesses
  • CWE-284

    Improper Access Control

  • CWE-798

    Use of Hard-coded Credentials

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Nov 15, 2026, 6:00 AM
Reserved
Sep 30, 2026, 12:50 PM
Status
Received
Published
Nov 15, 2026, 7:16 AM
Modified
Nov 15, 2026, 7:16 AM