Skip to content
PluginCanary
Limited data: this plugin has under 1,000 active installs and less than 12 weeks of history with us, so we show signals but no status band yet.

Paymentfor Gateway for WooCommerce

by paymentfor · 90+ active installs · Checked 3 Nov 2026
Limited data

Limited data: Paymentfor Gateway for WooCommerce has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

96/ 100 Canary Score
Sub-scores for Paymentfor Gateway for WooCommerce
Ownership100
Maintenance100
Security90
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Paymentfor Gateway for WooCommerce still maintained?
Yes. Last release 6 Oct 2026, 7 releases in the last 24 months. 6 Oct 2026 · wordpress.org
Who owns Paymentfor Gateway for WooCommerce, and has it changed hands?
No change recorded. Main committer paymentfor since Jan 2026. 3 Nov 2026 · SVN log
Was Paymentfor Gateway for WooCommerce removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Paymentfor Gateway for WooCommerce safe?
1 known vulnerability, fixed (latest in 1.0.6). Not on the exploited list. 14 Oct 2026 · Wordfence Intelligence
Is the latest Paymentfor Gateway for WooCommerce update safe to install?
No ownership change before 1.0.6. No one-star spike after it. 6 Oct 2026 · Release history

Active signals

Facts we detected, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Ownership timeline

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

Committers and their active periods
plugin-master20 Nov 2025 to 20 Nov 2025, 1 commits
paymentfor15 Jan 2026 to 6 Oct 2026, 17 commits

2 committers recorded. No ownership change since 2025.

Maintenance

Last release
29 days ago
Releases, 24 months
7
Tested up to
7.1 current
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for Paymentfor Gateway for WooCommerce
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20263
Q2 20261
Q3 20262
Q4 20261

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

Reputation

Last 90 days: no reviews.

Rating distribution
5 star0
4 star0
3 star0
2 star0
1 star0

Security record

1 vulnerability in 24 months, patched (latest fixed in 1.0.6).

Show 1 patched vulnerability
PublishedIssueCVSSAffectedFixed inDays to patch
14 Oct 2026Paymentfor Gateway for WooCommerce < 1.0.6 - Unauthenticated Arbitrary Order Status Manipulation7.3< 1.0.61.0.6Patched before disclosure

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

Support history appears after our first snapshots of the forum counts.

Momentum

90+ active installs. History builds with each weekly snapshot.

Momentum history builds with each snapshot.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

No healthier plugin in the same category yet.

Facts

Version1.0.6
Authorpaymentfor
Added15 Jan 2026
Last updated6 Oct 2026
Active installs90+
Requires WordPress5.6
Tested up to7.1.4
Requires PHP7.4
Categorynot stated
Tagspaypay, credit card, woocommerce, payment gateway, convenience store

Questions

Is Paymentfor Gateway for WooCommerce still maintained?

Yes. Last release 6 Oct 2026, 7 releases in the last 24 months.

Who owns Paymentfor Gateway for WooCommerce, and has it changed hands?

No change recorded. Main committer paymentfor since Jan 2026.

Was Paymentfor Gateway for WooCommerce removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026.

Is Paymentfor Gateway for WooCommerce safe?

1 known vulnerability, fixed (latest in 1.0.6). Not on the exploited list.

Is the latest Paymentfor Gateway for WooCommerce update safe to install?

No ownership change before 1.0.6. No one-star spike after it.

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