Fortis For Woocommerce
Approved changes feed: RSS · Atom
cpe:2.3:a:fortispay:fortis_for_woocommerce:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Fortispay (8f61976c-4c5f-5b3a-ae36-267b2aa9fcbc) |
|---|---|
| Product | Fortis For Woocommerce (a026f09d-06ef-5c42-a099-917e842a10c0) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-0679 |
vulnerable | 2026-06-08 07:47:12.907446 |
Fortis for WooCommerce <= 1.2.0 - Missing Authorization to Unauthenticated Arbitrary Order Status Update to Paid via 'wc-api' Endpoint
MEDIUM (5.3)
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.
Published: 2026-02-04T08:25:31.970Z
Updated: 2026-04-08T17:11:54.036Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.