# CVE-2026-15208: RegistrationMagic < 6.0.9.5 - Unauthenticated Payment Bypass via Amount-Blind PayPal Verification

> An unauthenticated attacker can bypass payment verification in RegistrationMagic by reusing low-value PayPal captures to finalize paid registrations.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-x5h9-fc29-gm85

## What is CVE-2026-15208?

CVE-2026-15208 is a medium-severity vulnerability in Unknown RegistrationMagic, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The RegistrationMagic WordPress plugin before 6.0.9.5 does not compare the verified PayPal capture's amount, currency, payee, or prior use against the registration it is finalising: its server-side check only confirms the capture status is COMPLETED. An unauthenticated attacker can therefore finalise an expensive paid registration with any genuinely-completed low-value capture, and replay a single capture across unlimited registrations because captures are not de-duplicated.

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

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


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

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

## Is CVE-2026-15208 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15208 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15208 is a medium-severity vulnerability in Unknown RegistrationMagic, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15208 exists.

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

## Sources

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

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