Fortis for WooCommerce <= 1.2.0 - Missing Authorization to Unauthenticated Arbitrary Order Status Update to Paid via 'wc-api' Endpoint
Strategic Overview
- Status
- Patched in 1.3.0
- Affected Plugin
- Fortis for WooCommerce
- Affected Version
<= 1.2.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-0679
At a glance
CVE-2026-0679 is a medium-severity Missing Authorization vulnerability in the Fortis for WooCommerce WordPress plugin, affecting versions <= 1.2.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.3.0; sites on affected versions should update now. Disclosed February 2026, reported by Md. Moniruzzaman Prodhan (NomanProdhan).
Vulnerability Overview
The Fortis for WooCommerce plugin for WordPress is vulnerable to authorization bypass due to an inverted nonce check in the 'check_fortis_notify_response' function in all versions up to, and including, 1.2.0. This makes it possible for unauthenticated attackers to update arbitrary WooCommerce order statuses to paid/processing/completed, effectively allowing them to mark orders as paid without payment.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Fortis for WooCommerce <= 1.2.0 carries this weakness at check_fortis_notify_response, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Fortis for WooCommerce the fix is 1.3.0: builds <= 1.2.0 are affected, anything from 1.3.0 onward is not.
Remediation
Update to version 1.3.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Fortis for WooCommerce 1.3.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Fortis for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C