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

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Sipay Electronic Money and Payment Services Inc. / WooCommerce Virtual POS Module: ≥ 26.8.3; < 26.9.1 (affected, semver). Source: CNA: TR-CERT

## Severity and prioritization

- CVSS 3.1: 9.1 (critical); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N; source: CNA: TR-CERT

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-306, CWE-354

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1520 (CNA: TR-CERT; government-resource)

## Provenance

- CNA: TR-CERT: https://www.cve.org/CVERecord?id=CVE-2026-85632; retrieved 2026-11-11; source updated 2026-11-11

Revision: 2bff151f69c9ff9592e9ff4d10fec5ef4c9be9c343102500b7653b6ebb21c81e

Canonical: https://y2.dev/cve/CVE-2026-85632

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.