LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0679: Fortis for WooCommerce <= 1.2.0 - Missing Authorization to Unauthenticated Arbitrary Order Status Update to Paid via 'wc-api' Endpoint

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A flaw in the Fortis for WooCommerce WordPress plugin can let an unauthenticated person mark WooCommerce orders as paid, processing, or completed without real payment. The direct business risk is fraudulent order fulfillment, revenue loss, and order reconciliation problems on affected stores.

Executive priority

Treat as a near-term ecommerce integrity issue, not a full site takeover. Prioritize affected revenue-generating stores because attackers could cause shipment or service delivery without payment. Validate exposure and update or disable quickly.

Technical view

CVE-2026-0679 is a missing authorization issue caused by an inverted nonce check in check_fortis_notify_response. Versions up to and including 1.2.0 are reported affected. The issue is reachable over the network via a wc-api endpoint, requires no login or user interaction, and has CVSS 3.1 score 5.3.

Likely exposure

Exposure is limited to WordPress sites running WooCommerce with Fortis for WooCommerce version 1.2.0 or earlier enabled. Public sources do not identify other affected products. Internet-facing stores are the primary concern because the vulnerable path is unauthenticated and network reachable.

Exploitation context

The CVE is not listed as KEV in the provided data, and no cited source states active exploitation. However, the vulnerability details and affected code references are public, and the attack requires no authentication, making timely validation important for ecommerce environments.

Researcher notes

The provided description attributes the flaw to CWE-862 and an inverted nonce check in check_fortis_notify_response. CVSS indicates integrity-only impact. Sources include Wordfence and WordPress Trac code references, but the bundle does not explicitly name a fixed version or confirm exploitation.

Mitigation direction

  • Identify all WordPress stores using Fortis for WooCommerce.
  • Update Fortis for WooCommerce beyond 1.2.0 if a fixed release is available.
  • If no fixed release is available, follow vendor guidance immediately.
  • Temporarily disable the plugin or affected payment workflow if business risk is unacceptable.
  • Review recent completed, processing, or paid orders for payment mismatches.

Validation and detection

  • Check installed Fortis for WooCommerce version on each WooCommerce site.
  • Confirm whether the plugin is active and handling Fortis payment notifications.
  • Review WooCommerce order history for paid statuses without matching payment records.
  • Monitor web logs for unusual unauthenticated wc-api requests related to Fortis.
  • Track vendor, Wordfence, and WordPress plugin repository updates.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0679 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-0679Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
fortispayFortis for WooCommerce0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.