# CVE-2026-87838: Wava Payment 0.3.1 - 0.3.9 - Unauthenticated Merchant Credential Overwrite via Install Webhook


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-hqf7-665r-7343

## What is CVE-2026-87838?

CVE-2026-87838 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 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.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-87838 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87838 is a medium-severity vulnerability in Unknown Wava Payment Plugin, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-87838 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-87838/ (Markdown: https://insights.sbomify.com/CVE-2026-87838/index.md)
```

## Sources

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

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