# CVE-2026-88928: PAYCOMET for WooCommerce 5.36 - 5.45 - Unauthenticated Stored Payment Token Overwrite via Signature Verification Bypass


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-jcp7-hvh9-8xxq

## What is CVE-2026-88928?

CVE-2026-88928 is a medium-severity vulnerability in Unknown PAYCOMET for WooCommerce, published on 29 Oct 2026. 

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-88928?


## How do I fix CVE-2026-88928?

No fix has been published for CVE-2026-88928 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-88928 being exploited?

There is no known exploitation of CVE-2026-88928 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88928 and fix it if it is affected.

What it is: CVE-2026-88928 is a medium-severity vulnerability in Unknown PAYCOMET for WooCommerce, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-88928 in the wild and no public exploit code.

Affected product: Unknown PAYCOMET for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88928/ (Markdown: https://insights.sbomify.com/CVE-2026-88928/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88928
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88928
- OSV: https://osv.dev/vulnerability/CVE-2026-88928

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88928/
Summaries are generated and may contain mistakes; the official description above is the record.