# CVE-2026-77826: Auth bypass in RegistrationMagic

> Unauthenticated attackers can bypass authentication by exploiting missing Facebook token audience validation, allowing them to log in as existing users or create new accounts.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Sep 2026
- **Updated:** 6 Sep 2026
- **Also known as:** GHSA-99w4-v9vm-vmmw

## What is CVE-2026-77826?

CVE-2026-77826 is a high-severity authentication bypass vulnerability in Unknown RegistrationMagic, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The RegistrationMagic  WordPress plugin before 6.0.9.9 does not verify which application a Facebook access token was issued to before accepting it as proof of identity, allowing unauthenticated attackers to log in as an existing user whose token they can obtain, or to create and log into a new account even when user registration is disabled.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-77826 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77826 is a high-severity authentication bypass vulnerability in Unknown RegistrationMagic, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-77826 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-77826/ (Markdown: https://insights.sbomify.com/CVE-2026-77826/index.md)
```

## Sources

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

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