CVE-2026-88928

PAYCOMET for WooCommerce 5.36 - 5.45 - Unauthenticated Stored Payment Token Overwrite via Signature Verification Bypass

Published Oct 29, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
The PAYCOMET for WooCommerce WordPress plugin before 5.46 does not verify the cryptographic signature on its payment notification endpoint when the request references a tokenisation operation, allowing unauthenticated attackers to overwrite the stored payment token associated with existing orders and delete saved card records.

Analysis

AI-generated

Technical impact

PAYCOMET for WooCommerce versions 5.36 through 5.45 do not verify the cryptographic signature on their payment notification endpoint when the request involves a tokenisation operation. This allows an unauthenticated attacker to overwrite the stored payment token tied to existing orders and to delete saved card records. The attacker can therefore alter payment details for future transactions, potentially redirect payments, erase card data, cause loss of customer trust, and lead to financial loss or regulatory non‑compliance.

Affected Systems

The vulnerability affects the PAYCOMET for WooCommerce WordPress plugin for all versions 5.36 through 5.45 inclusive. No other vendors or products are impacted according to the available data.

Risk and Exploitability

The CVSS score is 6.5, and the EPSS score is 0.00137 (about 0.14%), but the lack of authentication and signature verification indicates a high potential impact. Attacks are likely possible against the exposed payment notification endpoint, which may be reached by an external payment gateway or by an attacker who can craft HTTP requests. If the attacker can trigger the notification, they can tamper with stored payment tokens without needing credentials to the WordPress site. Although no known exploits are listed in the KEV catalog, the severity of the exploitation remains significant.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade PAYCOMET for WooCommerce to version 5.46 or later, which adds proper signature verification to the payment notification endpoint.
  • If an immediate upgrade is not possible, limit access to the notification endpoint by allowing only the known IP addresses of the payment gateway, blocking all other requests.
  • Implement server‑side validation to ensure that every notification request includes a cryptographically valid signature before accepting or processing it.
  • Manually audit the stored payment tokens in the database and remove any suspicious or duplicate entries that may have been created during the vulnerability window.

Generated by OpenCVE AI on October 29, 2026 at 16:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions paycomet For Woocommerce
Vendors & Products Wordpress-extensions
Wordpress-extensions paycomet For Woocommerce
Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-287
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
Description The PAYCOMET for WooCommerce WordPress plugin before 5.46 does not verify the cryptographic signature on its payment notification endpoint when the request references a tokenisation operation, allowing unauthenticated attackers to overwrite the stored payment token associated with existing orders and delete saved card records.
Title PAYCOMET for WooCommerce 5.36 - 5.45 - Unauthenticated Stored Payment Token Overwrite via Signature Verification Bypass
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 29, 2026, 10:56 AM
Reserved
Sep 10, 2026, 2:12 PM
Status
Deferred
Published
Oct 29, 2026, 6:17 AM
Modified
Oct 29, 2026, 3:18 PM