Skip to content
Laskyr

Plugins · woocommerce-for-paygent-payment-main · data as of 2026-11-04

Is PAYGENT for WooCommerce safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.0.1)

As of 2026-11-04. 1 issue is on record for older versions; version 2.4.7 or newer fixes all of them that state a fix.

Latest version
3.0.1
Last updated
2026-10-23
Active installs
100+
Known issues on record
1
Unpatched in latest
0
Tested up to WP
7.1.4

PAYGENT Payment Gateway plugin provides all popular online payment methods for your Woocommerce webshop in Japan. — by shohei.tanaka

What to do

  1. Update to the latest version (3.0.1). Anything older than 2.4.7 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get woocommerce-for-paygent-payment-main --field=version shows what you run; wp plugin update woocommerce-for-paygent-payment-main updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.3 CVE-2025-14078 · published 2026-01-17

Missing authorization check in PAYGENT for WooCommerce (2.4.6 and older)

Affected
2.4.6 and older
Fixed in
2.4.7 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The PAYGENT for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 2.4.6. This is due to missing authorization checks on the paygent_check_webhook function combined with the paygent_permission_callback function unconditionally returning true on line 199. This makes it possible for unauthenticated attackers to manipulate payment callbacks and modify order statuses by sending forged payment notifications via the `/wp-json/paygent/v1/check/` endpoint.

NVD CVE-2025-14078Wordfence advisoryCode change (fix)Plugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
PAYGENT for WooCommerce vulnerability status badge
<a href="https://laskyr.com/plugins/woocommerce-for-paygent-payment-main"><img src="https://laskyr.com/plugins/woocommerce-for-paygent-payment-main/badge.svg" alt="PAYGENT for WooCommerce vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit