# CVE-2026-87837: Wava Payment 0.3.1 - 0.3.9 - Unauthenticated Order Status Change via Payment Webhook


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-8mpv-23rw-jfjx

## What is CVE-2026-87837?

CVE-2026-87837 is a medium-severity vulnerability in Unknown Wava Payment Plugin, published on 21 Oct 2026. 

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-87837?


## How do I fix CVE-2026-87837?

No fix has been published for CVE-2026-87837 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-87837 being exploited?

There is no known exploitation of CVE-2026-87837 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-87837 and fix it if it is affected.

What it is: CVE-2026-87837 is a medium-severity vulnerability in Unknown Wava Payment Plugin, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-87837 in the wild and no public exploit code.

Affected product: Unknown Wava Payment Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-87837/ (Markdown: https://insights.sbomify.com/CVE-2026-87837/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-87837
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-87837
- OSV: https://osv.dev/vulnerability/CVE-2026-87837

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-87837/
Summaries are generated and may contain mistakes; the official description above is the record.