Is Payaza safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (0.3.13). As of 2026-11-04. 1 issue is on record for older versions; version 0.3.10 or newer fixes all of them that state a fix. Keep Payaza on the latest version (0.3.13) and remove it if you do not use it.

Which versions of Payaza are vulnerable?

Known issues on record (newest first): Missing authorization check (0.3.8 and older, fixed in 0.3.10). The full list with sources is on this page.

What is the latest version of Payaza?

0.3.13, according to wordpress.org (last updated 2026-05-25). It has 300+ active installs.

What should I do if my Payaza is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update payaza). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · payaza · data as of 2026-11-04

Is Payaza safe? Known vulnerabilities and latest version

Latest version: 0.3.13
Last updated: 2026-05-25
Active installs: 300+
Known issues on record: 1
Unpatched in latest: 0
Tested up to WP: 6.9.11 · PHP 7.4+

Effortlessly start accepting card payments and bank transfers and other payment methods with the official Payaza Plugin for WooCommerce. — by Adedeji A

What to do

Update to the latest version (0.3.13). Anything older than 0.3.10 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
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 payaza --field=version shows what you run; wp plugin update payaza 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-12355 · published 2025-12-05

Missing authorization check in Payaza (0.3.8 and older)

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

Details from the advisory

The Payaza plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wp_ajax_nopriv_update_order_status' AJAX endpoint in all versions up to, and including, 0.3.8. This makes it possible for unauthenticated attackers to update order statuses.

NVD CVE-2025-12355 Wordfence advisory wordpress.org

Recent activity

2026-05-25 — latest release on wordpress.org (0.3.13).
2025-12-05 — Missing authorization check disclosed (CVE-2025-12355), fixed in 0.3.10.

Free. We check the CVE feeds every day and email you only when a new issue for Payaza (payaza) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/payaza (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/payaza"><img src="https://laskyr.com/plugins/payaza/badge.svg" alt="Payaza vulnerability status"></a>

← Check another plugin · Free hacked-site scan