CVE-2026-0679

5.3 MEDIUM

📋 TL;DR

The Fortis for WooCommerce WordPress plugin has an authorization bypass vulnerability that allows unauthenticated attackers to change WooCommerce order statuses to paid/processing/completed without payment. This affects all WordPress sites using the plugin version 1.2.0 or earlier. Attackers can fraudulently mark orders as paid, potentially causing financial losses and order fulfillment issues.

💻 Affected Systems

Products:
  • Fortis for WooCommerce WordPress plugin
Versions: All versions up to and including 1.2.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects WordPress installations with WooCommerce and the Fortis payment gateway plugin enabled.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could mark all orders as paid, causing massive financial losses from shipping products without payment, inventory depletion, and complete disruption of e-commerce operations.

🟠

Likely Case

Attackers selectively mark high-value orders as paid to receive expensive products without payment, causing direct financial losses and inventory issues.

🟢

If Mitigated

With proper monitoring and order verification processes, impact is limited to temporary order status confusion requiring manual correction.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability is simple to exploit due to inverted nonce check logic. Attackers can send crafted requests to the notification endpoint without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.2.1 or later

Vendor Advisory: https://plugins.trac.wordpress.org/browser/fortis-for-woocommerce

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find Fortis for WooCommerce. 4. Click 'Update Now' if update available. 5. If no update, manually download version 1.2.1+ from WordPress.org and replace plugin files.

🔧 Temporary Workarounds

Disable Fortis Plugin

all

Temporarily disable the vulnerable plugin until patched

wp plugin deactivate fortis-for-woocommerce

Block Notification Endpoint

linux

Block access to the vulnerable notification endpoint via web server configuration

# Apache: <LocationMatch "\/wc-api\/fortis_notify">
    Order deny,allow
    Deny from all
</LocationMatch>
# Nginx: location ~* \/wc-api\/fortis_notify { deny all; }

🧯 If You Can't Patch

  • Disable the Fortis for WooCommerce plugin immediately and use alternative payment gateway
  • Implement manual order verification process requiring admin approval before order fulfillment

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin > Plugins > Fortis for WooCommerce. If version is 1.2.0 or earlier, you are vulnerable.

Check Version:

wp plugin get fortis-for-woocommerce --field=version

Verify Fix Applied:

After updating, verify plugin version shows 1.2.1 or later in WordPress admin plugins page.

📡 Detection & Monitoring

Log Indicators:

  • Multiple POST requests to /wc-api/fortis_notify from unauthenticated users
  • Rapid order status changes from pending to processing/completed without corresponding payment transactions

Network Indicators:

  • Unusual traffic patterns to WooCommerce API endpoints from unexpected IPs
  • POST requests to fortis_notify endpoint without proper authentication headers

SIEM Query:

source="wordpress.log" AND (uri_path="/wc-api/fortis_notify" AND http_method="POST" AND user="-")

🔗 References

📤 Share & Export