Skip to content
Laskyr

Plugins · wava-payment · data as of 2026-11-04

Is Wava Payment Plugin safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (0.3.10)

As of 2026-11-04. 3 issues are on record for older versions; version 0.3.10 or newer fixes all of them that state a fix.

Latest version
0.3.10
Last updated
2026-10-13
Active installs
100+
Known issues on record
3
Unpatched in latest
0
Tested up to WP
6.8.12 · PHP 7.4+

Acepta pagos con Nequi, DaviPlata y Bre-B en WooCommerce. Conecta Stripe para ventas internacionales y gestiona tu tesorería con Wava. — by Wava.co

What to do

  1. Update to the latest version (0.3.10). Anything older than 0.3.10 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 wava-payment --field=version shows what you run; wp plugin update wava-payment updates it.

Check your version

Known vulnerabilities

3 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-2026-87837 · published 2026-10-21

Missing authorization check in Wava Payment Plugin (0.3.1 up to (not including) 0.3.10)

Affected
0.3.1 up to (not including) 0.3.10
Fixed in
0.3.10
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory

The Wava Payment Plugin WordPress plugin before 0.3.10 does not verify the authenticity of incoming payment-provider notifications, nor restrict who may send them, allowing unauthenticated attackers to change the status of any WooCommerce order in the store, including marking an unpaid order as paid and completed, and cancelling other customers' orders. In versions up to 0.3.7 the response additionally returns the affected order's billing details, disclosing customer names, addresses, email addresses and phone numbers to the same unauthenticated caller.

NVD CVE-2026-87837WPScan advisory

medium 6.5 CVE-2026-87838 · published 2026-10-21

Missing authorization check in Wava Payment Plugin (0.3.1 up to (not including) 0.3.10)

Affected
0.3.1 up to (not including) 0.3.10
Fixed in
0.3.10
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory

The Wava Payment Plugin WordPress plugin before 0.3.10 does not perform any authorisation, nonce or origin verification on one of its public REST endpoints, allowing unauthenticated attackers to overwrite the stored credential that identifies the merchant account the store's payments are created against, to force the integration into a verified state the site owner never completed, and to remove the payment method from the store's checkout.

NVD CVE-2026-87838WPScan advisory

medium 5.3 CVE-2026-39609 · published 2026-04-08

Missing authorization check in Wava Payment Plugin (0.3.7 and older)

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

Missing Authorization vulnerability in Wava.co Wava Payment wava-payment allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Wava Payment: from n/a through <= 0.3.7.

NVD CVE-2026-39609Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Wava Payment Plugin vulnerability status badge
<a href="https://laskyr.com/plugins/wava-payment"><img src="https://laskyr.com/plugins/wava-payment/badge.svg" alt="Wava Payment Plugin 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