# CVE-2026-77793: RegistrationMagic < 6.0.9.9 - Unauthenticated Payment Bypass via Omitted Price Field

> Unauthenticated attackers can bypass payment validation to obtain activated accounts in RegistrationMagic by omitting the price field.

- **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:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-6gqp-ppxj-7jmc

## What is CVE-2026-77793?

CVE-2026-77793 is a medium-severity vulnerability in Unknown RegistrationMagic, published on 2 Sep 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.9 does not validate the total price of a paid registration server-side, allowing unauthenticated users to complete a paid registration without paying and obtain an activated account.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

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


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

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

## Is CVE-2026-77793 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77793 is a medium-severity vulnerability in Unknown RegistrationMagic, published on 2 Sep 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-77793 in the wild and no public exploit code.

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-77793/ (Markdown: https://insights.sbomify.com/CVE-2026-77793/index.md)
```

## Sources

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

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