Skip to content
PluginCanary

Piraeus Bank WooCommerce Payment Gateway

by Papaki (Enartia S.A.) · 3,000+ active installs · Checked 3 Nov 2026
Avoid1 Critical

Avoid: vulnerability published 18 Aug 2026 still has no fix after 14 days.

39/ 100 Canary Score

Capped at 39 while a vulnerability has no patch.

Sub-scores for Piraeus Bank WooCommerce Payment Gateway
Ownership100
Maintenance100
Security30
Support70
Reputation70

How the score works

Active signals

Facts we detected, with links to the source.

  • CriticalSEC-2Vulnerability published 18 Aug 2026 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.1 Sep 2026Evidence

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
enartia27 Mar 2017 to 19 Jan 2026, 50 commits
georgekapsalakis28 Jan 2019 to 28 Feb 2022, 19 commits
radishconcepts16 Oct 2026 to 16 Oct 2026, 2 commits

New committer radishconcepts made a first commit on 16 Oct 2026.

Maintenance

Last release
19 days ago
Releases, 24 months
1
Tested up to
7.1 current
Requires PHP
7.4 supported 8.2+
Releases per quarter for Piraeus Bank WooCommerce Payment Gateway
Q1 20240
Q2 20240
Q3 20248
Q4 20241
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20260
Q4 20261

Last release 16 Oct 2026. Tested with WordPress 7.1 (current).

Support

0% of 3 support threads resolved in the last 2 months.

Security record

Source: Wordfence Intelligence.

Reputation

Lifetime rating 3.9 from 35 ratings. Quarterly trends appear as new reviews arrive.

Rating distribution
5 star24
4 star2
3 star0
2 star0
1 star9

Momentum

3,000+ active installs. History builds with each weekly snapshot.

Weekly downloads, last 27 weeks
Weekly downloads for Piraeus Bank WooCommerce Payment Gateway
4 May 202659
11 May 2026113
18 May 2026140
25 May 2026113
1 Jun 2026111
8 Jun 2026123
15 Jun 202682
22 Jun 202687
29 Jun 202679
6 Jul 2026102
13 Jul 202686
20 Jul 202683
27 Jul 2026111
3 Aug 2026131
10 Aug 2026106
17 Aug 2026112
24 Aug 2026111
31 Aug 2026118
7 Sep 2026123
14 Sep 2026124
21 Sep 2026126
28 Sep 2026149
5 Oct 2026143
12 Oct 2026250
19 Oct 2026224
26 Oct 2026208
2 Nov 202642

Weekly downloads over the last 4 weeks are 50% above the 27-week average.

Healthier alternatives

Same category, higher Canary Score. Never sponsored.

WooPayments: Integrated WooCommerce PaymentsScore 93 · 800,000+FunnelKit Payment Gateway for Stripe WooCommerceScore 92 · 20,000+Payment Plugins for Stripe WooCommerceScore 91 · 100,000+WooCommerce Payfast GatewayScore 91 · 30,000+Smart COD for WooCommerceScore 91 · 30,000+

Facts

Version3.2.0
AuthorPapaki (Enartia S.A.)
Added22 Mar 2017
Last updated16 Oct 2026
Active installs3,000+
Requires WordPress6.4
Tested up to7.1.4
Requires PHP7.4
CategoryE-commerce & Shopping
Tagsecommerce, woocommerce, payment gateway

Other plugins by this author: Pay in Store WooCommerce Payment Gateway, Viva Payments - Viva Wallet WooCommerce Payment Gateway, Skroutz & Bestprice XML feed for WooCommerce

Questions

Is Piraeus Bank WooCommerce Payment Gateway still maintained?

Piraeus Bank WooCommerce Payment Gateway was last updated on 16 Oct 2026. Its Canary status is Avoid.

Is Piraeus Bank WooCommerce Payment Gateway safe?

Piraeus Bank WooCommerce Payment Gateway has 1 published vulnerability with no patched version. Its Canary status is Avoid.

Who owns Piraeus Bank WooCommerce Payment Gateway?

The wordpress.org author is Papaki (Enartia S.A.). Recent committers: radishconcepts, enartia, georgekapsalakis, plugin-master. New committer radishconcepts made a first commit on 16 Oct 2026.

What can I use instead of Piraeus Bank WooCommerce Payment Gateway?

Plugins in the same category with a higher Canary Score: WooPayments: Integrated WooCommerce Payments, FunnelKit Payment Gateway for Stripe WooCommerce, Payment Plugins for Stripe WooCommerce, WooCommerce Payfast Gateway, Smart COD for WooCommerce.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews, Wordfence Intelligence.Plugin data refreshed 3 Nov 2026.Report a data issue