Skip to main content

Wava Payment Plugin CVE-2026-87837

| EUVDEUVD-2026-107086 MEDIUM
Missing Authorization (CWE-862)
2026-10-21 WPScan GHSA-8mpv-23rw-jfjx
5.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify store running Wava Payment Plugin
  2. Exploit
    Forge payment-provider notification to callback endpoint
  3. Execution
    Spoof unverified 'paid/completed' status change
  4. Impact
    Obtain goods free, cancel orders, or leak billing data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The target store must have the Wava Payment Plugin (version 0.3.1 up to but not including 0.3.10) installed and active alongside WooCommerce. Exploitation requires sending a crafted HTTP request to the plugin's payment-provider notification/callback endpoint; because the plugin neither verifies notification authenticity nor restricts the sender, no authentication, token, or valid provider signature is needed and default configurations are vulnerable. The customer-billing-data disclosure is additionally limited to versions up to 0.3.7 (fixed-but-still-vulnerable 0.3.8/0.3.9 retain only the order-tampering issue). Practical limits: the attacker generally needs to reference valid WooCommerce order IDs (typically sequential/enumerable) to target specific orders, and the store must expose the plugin endpoint to the internet.

Impact

This is a genuine but moderate-priority issue whose signals mostly align. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes the easiest possible exploitation profile - remote, unauthenticated, low-complexity, no user interaction - which is fully consistent with the description of an unauthenticated attacker forging payment-provider notifications. The base score of 5.3 is held down to MEDIUM only because the vendor/NVD vector scores confidentiality as C:N and captures just a single I:L integrity impact. However, the description explicitly states that versions up to 0.3.7 also leak customer names, addresses, emails and phone numbers to the unauthenticated caller, so the published vector appears to UNDERSTATE real impact for that version range - confidentiality should arguably be C:L, raising the true severity. POC/exploit code is publicly available (WPScan), so weaponization barrier is low, but there is NO CISA KEV listing and NO EPSS score was provided, so there is no evidence of active or widespread exploitation and no probabilistic exploitation estimate to weigh. No SSVC decision data (exploitation status, automatable, technical impact) was supplied. Net: a readily exploitable, publicly-documented authorization flaw with direct financial-fraud consequences (free goods via fake 'paid' status) and order-cancellation sabotage, but real-world blast radius is constrained by the apparently niche deployment of this specific plugin.

Exploit ScenarioDerived

An attacker identifies an online store running the Wava Payment Plugin and sends a forged payment-provider notification directly to the plugin's unauthenticated callback endpoint, marking their own unpaid WooCommerce order as 'paid/completed' to receive goods or services for free. Against stores on version 0.3.7 or earlier, the same forged request returns the target order's billing details, letting the attacker harvest other customers' names, addresses, emails and phone numbers. Public exploit details are available via the WPScan advisory, lowering the skill required.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Unauthenticated order manipulation in the Wava Payment Plugin for WordPress (0.3.1 through 0.3.9) allows remote attackers to forge payment-provider notifications and change WooCommerce order states, including marking unpaid orders paid and completed and cancelling other customers' orders. Versions through 0.3.7 also return billing details such as names, addresses, emails, and phone numbers to the same unauthenticated caller. Publicly available exploit code exists, and the vendor has released 0.3.10 to address the missing authorization and authenticity checks.

RemediationAI

Vendor-released patch: 0.3.10; upgrade the Wava Payment Plugin to 0.3.10 or later and confirm the callback endpoint enforces provider authenticity. If upgrade cannot be completed immediately, disable the plugin, accepting that payment processing and its callback stop and checkout may be disrupted, or restrict the notification endpoint at the web server or WAF to the payment provider's published source addresses and validate provider signatures at a proxy where possible; IP allowlisting can break legitimate callbacks if provider ranges change and is not a substitute for patching. Review WooCommerce order status changes and, for stores on 0.3.7 or earlier, check whether billing details were exposed. Advisory: https://wpscan.com/vulnerability/76da1b69-aa79-4e9e-a97a-bbaefdeb65fe/

Affected VersionsENISA

Wava Payment Plugin 0.3.1 <0.3.10

Affected Packages

euvd wava_payment_plugin fix: 0.3.10

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The plugin integrates WooCommerce with a payment provider and exposes a notification/callback endpoint. Under CWE-862 (Missing Authorization), it does not verify that incoming notifications are authentic and does not restrict who can send them, so the handler trusts the request to transition order status. Because WooCommerce order IDs are often sequential and enumerable, an attacker can target known orders. The CPE entry is a wildcard with an unknown vendor, reflecting incomplete product attribution. The billing-data exposure in versions up to 0.3.7 stems from the same unauthenticated callback returning order billing fields; 0.3.8 and 0.3.9 fix that disclosure but still permit order-state tampering until 0.3.10. The assessed impact is limited integrity and confidentiality, not full store takeover.

Know when Wava Payment Plugin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
vuln.today AI 6.5 MEDIUM

Remote, unauthenticated, low-complexity forged request (AV:N/AC:L/PR:N/UI:N); I:L for order-status tampering and C:L for billing-data disclosure in versions ≤0.3.7; no availability loss.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

4
CVSS changed
Oct 21, 2026 - 11:22 NVD
5.3 (MEDIUM)
Patch available
Oct 21, 2026 - 07:01 EUVD
CVE Published
Oct 21, 2026 - 06:00 cve.org
MEDIUM 5.3
CVE Published
Oct 21, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
obscure WooCommerce payment plugin, limited WordPress install base
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy