---
id: "CVE-2026-88928"
kind: "vulnerability"
aliases: ["CVE-2026-88928"]
title: "PAYCOMET for WooCommerce: unsigned payment callbacks let attackers alter saved cards"
severity: "high"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "paycomet", "payments", "woocommerce", "wordpress"]
not_affected_if: ["plugin-5.46-or-later"]
published_at: "2026-10-29T06:17:24+00:00"
first_seen_at: "2026-10-29T06:53:14+00:00"
updated_at: "2026-10-29T06:54:34+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-88928", "first_seen_at": "2026-10-29T06:53:14+00:00"}]
---

# PAYCOMET for WooCommerce: unsigned payment callbacks let attackers alter saved cards

The PAYCOMET for WooCommerce WordPress plugin before 5.46 does not verify the cryptographic signature on its payment notification endpoint when a request references a tokenisation operation. An unauthenticated attacker can overwrite stored payment tokens tied to existing orders and delete saved card records.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of the PAYCOMET for WooCommerce plugin in the WordPress admin plugins list; versions below `5.46` are in the affected range.
- Review the plugin's payment notification endpoint and whether it is reachable from the internet.

## Fix

- PAYCOMET for WooCommerce: `5.46`

## Timeline

- 2026-10-29T06:53:14+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-88928

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_