# CVE-2026-9242: RegistrationMagic <= 6.0.8.6 - Authenticated (Subscriber+) Authentication Bypass via Forged PayPal IPN Request

> Unauthenticated attackers can bypass authentication and log in as any user, including administrators, by forging PayPal IPN requests to poison payment logs.

- **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:** 27 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-jxxc-m933-38gm

## What is CVE-2026-9242?

CVE-2026-9242 is a medium-severity authentication bypass vulnerability in metagauss RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login, published on 27 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to Authentication Bypass via Insufficient Verification of Data Authenticity in all versions up to and including 6.0.8.6. This is due to the PayPal IPN `callback` handler being registered as a nopriv AJAX action with no authentication or nonce requirement, and critically because the handler updates the payment log database row with attacker-controlled POST data — including `payment_status` and the `custom` field encoding the target `user_id` — before PayPal IPN validation is performed, meaning the database remains poisoned even when validation subsequently fails. This makes it possible for unauthenticated attackers to authenticate as any WordPress user, including administrators, by submitting a forged IPN request that overwrites a payment log entry's `user_id` with that of a target account, then visiting the success return URL with a legitimately obtained security hash to cause the plugin to issue real WordPress authentication cookies for the targeted account.

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

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


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

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

## Is CVE-2026-9242 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9242 is a medium-severity authentication bypass vulnerability in metagauss RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login, published on 27 Jun 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-9242 in the wild and no public exploit code.

Affected product: metagauss RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login. 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-9242/ (Markdown: https://insights.sbomify.com/CVE-2026-9242/index.md)
```

## Sources

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

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