CVE-2026-0679
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Fortis for WooCommerce plugin contains an inverted nonce check in the 'check_fortis_notify_response' function. A nonce is a security token used to validate that a request originates from an authorized source; the inverted logic means the check validates requests from unauthorized sources while rejecting legitimate ones. This allows any unauthenticated user to trigger order status updates, effectively marking orders as paid without any payment processing.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Fortis for WooCommerce plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Fortis for WooCommerce' or check the plugin directory wp-content/plugins/ for a folder named 'fortis-for-woocommerce' or similar. Check the plugin version listed in the plugin metadata.Affected if The plugin is installed and no patched version beyond 1.2.0 has been released yet, or the installed version is 1.2.0 or lower.
-
Confirm WooCommerce is activeVerify WooCommerce is installed and active in WordPress at Plugins > Installed Plugins, since this is a WooCommerce-specific plugin.Affected if WooCommerce is active and the Fortis plugin is installed, making the vulnerable code path reachable.
-
Locate the check_fortis_notify_response functionAccess the plugin files via file manager or FTP. Navigate to the plugin directory and search for the function named 'check_fortis_notify_response' in PHP files, typically in a file handling payment notifications or callbacks.Affected if The function exists in the plugin codebase, indicating the vulnerable code is present.
-
Inspect the nonce validation logicOpen the file containing check_fortis_notify_response and examine the nonce check logic. Look for inverted conditional statements (e.g., 'if (!wp_verify_nonce(...))' that allows access or 'if (empty($nonce))' that should block but instead permits).Affected if The nonce check uses inverted or incorrect logic that would validate requests from unauthorized sources instead of rejecting them.
You are affected if Fortis for WooCommerce is installed with version 1.2.0 or below, WooCommerce is active, and the plugin contains the check_fortis_notify_response function with inverted nonce validation logic.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Fortis for WooCommerce plugin to a version beyond 1.2.0 once available; if no patched version exists, disable the plugin or implement temporary network-level access controls to restrict the affected endpoint until a fix is released.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0679 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0679 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data