Piraeus Bank Woocommerce Payment Gateway
Approved changes feed: RSS · Atom
cpe:2.3:a:enartia:piraeus_bank_woocommerce_payment_gateway:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Enartia (e41dffa0-36fb-57e6-91b1-5cb5aecaa5aa) |
|---|---|
| Product | Piraeus Bank Woocommerce Payment Gateway (90c16731-7e85-53af-8a36-9d0cea8b31e5) |
| 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-2025-14460 |
vulnerable | 2026-06-08 07:06:34.522813 |
Piraeus Bank WooCommerce Payment Gateway <= 3.1.4 - Missing Authorization to Unauthenticated Arbitrary Order Status Change
MEDIUM (5.3)
The Piraeus Bank WooCommerce Payment Gateway plugin for WordPress is vulnerable to unauthorized order status modification in all versions up to, and including, 3.1.4. This is due to missing authorization checks on the payment callback endpoint handler when processing the 'fail' callback from the payment gateway. This makes it possible for unauthenticated attackers to change any order's status to 'failed' via the publicly accessible WooCommerce API endpoint by providing only the order ID (MerchantReference parameter), which can be easily enumerated as order IDs are sequential integers. This can cause significant business disruption including canceled shipments, inventory issues, and loss of revenue.
Published: 2026-01-07T09:21:04.538Z
Updated: 2026-04-08T17:26:39.127Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-0610 |
vulnerable | 2026-06-08 06:22:01.478059 |
Piraeus Bank WooCommerce Payment Gateway <= 1.6.5.1 - Unauthenticated SQL Injection
CRITICAL (9.8)
The Piraeus Bank WooCommerce Payment Gateway plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'MerchantReference' parameter in all versions up to, and including, 1.6.5.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Published: 2024-02-17T07:36:58.945Z
Updated: 2026-04-08T17:32:28.454Z 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.