On this page (7 sections)
A critical vulnerability, CVE-2026-85632, has been published for the WooCommerce Virtual POS Module from Sipay Electronic Money and Payment Services Inc. According to the GitHub Advisory Database entry, it combines missing authentication for a critical function with improper validation of an integrity check value, and it allows authentication bypass and manipulation of API messages via a man-in-the-middle position.
If you run a WooCommerce store that takes payments through this module, check your installed version now. The advisory says versions from 26.8.3 before 26.9.1 are affected, so 26.9.1 is the first version that is outside the affected range.
What was disclosed
The record was published on November 11, 2026 and describes two weaknesses in the same module. The first is missing authentication for a critical function (CWE-306). The second is improper validation of an integrity check value (CWE-354). The stated impact is authentication bypass and "Application API Message Manipulation via Man-in-the-Middle".
The NVD entry carries the same text as the GitHub advisory, so it is not a separate confirmation. The advisory also points to a Turkish national cyber security notice, TR-26-1520. At the time of writing, no other independent analysis is available.
What the weaknesses mean in plain terms
A payment module sits between your shop and a payment provider. It sends order details out and receives results back, such as whether a payment succeeded. Two safeguards normally protect that exchange: the module checks who is making a request, and it checks that a message has not been altered in transit.
CWE-306 means a function that should require proof of identity does not. CWE-354 means the check that proves a message is intact is not validated properly. Together, as the advisory describes, an attacker positioned between the parties could tamper with API messages and get past authentication. The advisory does not say which functions are affected or what a successful attack would let someone do to an order, and this article does not speculate beyond that.
- CVSS v3 base score shown in the advisory
- 9.1
- Attack vector
- Network
- Privileges required and user interaction
- None
- Confidentiality and integrity impact; availability none
- High
The vector string shown is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. In short: it can be attacked over the network, with low complexity, no account and no user action, and the impact is on data confidentiality and integrity rather than availability.
Who is exposed
- Stores using the Sipay WooCommerce Virtual POS Module at a version from 26.8.3 up to, but not including, 26.9.1.
- Agencies and hosts that manage WooCommerce shops for clients and may not know which payment modules are installed.
- Stores that installed the module recently, since the affected range starts at 26.8.3 and the fix is a nearby release.
Stores that do not use this module, or that already run 26.9.1 or later, are outside the range described in the advisory. The research does not say whether versions older than 26.8.3 are affected, so if you run an older release, ask the vendor rather than assuming.
How to check your exposure
Open the WordPress admin and go to Plugins, then find the Sipay Virtual POS entry and read its version. If you have shell access to the server, WP-CLI can list plugins with their versions. Run it from the WordPress root directory and look for the Sipay module in the output.
wp plugin list --fields=name,status,versionCompare the version with the affected range. Anything from 26.8.3 up to but not including 26.9.1 is in scope. The plugin's folder name is not given in the research, so identify the module by its title in the list.
What to do now
- Identify every WooCommerce site you manage that uses the Sipay Virtual POS Module and note its version.
- Back up the site and database before changing anything.
- Update the module to 26.9.1 or later, using the vendor's official release channel.
- If you cannot update right away, contact Sipay for guidance and consider temporarily switching to another payment method during the gap. The research does not describe an official workaround.
- Review recent orders and payment records for mismatches, such as orders marked paid without a matching payment at your provider.
- Make sure your store is served over HTTPS with a valid certificate, since the attack described needs a man-in-the-middle position.
- Read the vendor's and national CERT notices for further guidance, and check them again over the coming days.
Detection and monitoring
The sources give no indicators of compromise and report no exploitation, so there is no specific signature to search for. Practical monitoring is about spotting odd payment behavior and weak transport security.
- Watch for orders that changed status without a matching payment, or with amounts that differ from what the customer was charged.
- Review web server logs for unusual requests to the module's endpoints or callbacks, especially from unfamiliar addresses.
- Keep an eye on TLS certificate validity and changes to DNS records for your store domain, since interception attacks often rely on these.
A free SSL certificate checker can confirm your certificate and protocol setup, and certificate and DNS change monitoring can alert you if something on your domain changes unexpectedly. Neither addresses this vulnerability directly; the fix is the module update. For wider store hygiene, see the guide to security for online stores.
What is still unknown
- Which specific functions lack authentication, and what an attacker could do with them.
- Whether versions before 26.8.3 are affected.
- Whether the flaw is being exploited. None is reported in the sources, and the CVE is not listed in CISA KEV.
- Whether a public proof of concept exists. None is mentioned in the research.
Because the score is high and no authentication or user action is needed, treat the update as urgent even without reports of attacks. We will not state more than the advisory does until the vendor or other researchers publish details.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
