Piraeus Bank WooCommerce Payment Gateway
woo-payment-gateway-for-piraeus-bank · plugin
Known security vulnerabilities for Piraeus Bank WooCommerce Payment Gateway. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
1 critical · 3 exploitable without logging in · 1 with no official fix seen · latest Aug 18, 2026
Before you install
Do not install
- 1 record shows no fix in the latest wordpress.org release.
- 2 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 3.2.0 · last updated Oct 16, 2026 · 3K+ installs
wordpress.org status checked on Nov 16, 2026
Vulnerabilities
- Critical 9.8
CVE-2024-0610unauthenticated≤ 1.6.5.1
Piraeus Bank WooCommerce Payment Gateway <= 1.6.5.1 - Unauthenticated SQL Injection
- Medium 6.5
CVE-2026-73398unauthenticatedno fix seen
WordPress Piraeus Bank WooCommerce Payment Gateway plugin 3.2.0 - Broken Authentication vulnerability
- Medium 5.3
CVE-2025-14460unauthenticated≤ 3.1.4
Piraeus Bank WooCommerce Payment Gateway <= 3.1.4 - Missing Authorization to Unauthenticated Arbitrary Order Status Change
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (3.2.0) as affected.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.