# CVE-2026-126543: WWBN AVideo through 29.7.1 Wallet Credit Manipulation via PayPalYPT ipnV2.php

> Unauthenticated attackers can forward PayPal IPNs to AVideo to add wallet balance for chosen users; AVideo sites using PayPalYPT should care.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-5gg3-9jhh-xf86, GHSA-r4j2-2784-v3cx

## What is CVE-2026-126543?

CVE-2026-126543 is a high-severity business logic flaw vulnerability in WWBN AVideo, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WWBN AVideo through 29.7.1 contains an improper payment verification vulnerability in plugin/PayPalYPT/ipnV2.php that credits wallets from PayPal IPNs not bound to the site's merchant account. Unauthenticated attackers can forward genuine VERIFIED recurring-payment IPNs from their own PayPal account with a chosen users_id to add wallet balance each billing cycle.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

Only installations with a non-default setting turned on are exposed.


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

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

## Is CVE-2026-126543 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126543 is a high-severity business logic flaw vulnerability in WWBN AVideo, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126543 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: WWBN AVideo. 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-126543/ (Markdown: https://insights.sbomify.com/CVE-2026-126543/index.md)
```

## Sources

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

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