# CVE-2023-2499: RegistrationMagic <= 5.2.1.0 - Authentication Bypass

> Unauthenticated attackers can bypass authentication via Google social login to log in as any existing user, including administrators, if they know the email address.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 May 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2mx9-wcpw-c6gq

## What is CVE-2023-2499?

CVE-2023-2499 is a critical authentication bypass vulnerability in metagauss RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login, published on 16 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The RegistrationMagic plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 5.2.1.0. This is due to insufficient verification on the user being supplied during a Google social login through the plugin. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email.

Weakness: CWE-287 (Improper Authentication), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2023-2499?

It affects 1 product.


Products: Metagauss Registrationmagic.

## How do I fix CVE-2023-2499?

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

## Is CVE-2023-2499 being exploited?

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

## Other vulnerabilities in metagauss RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login

- [CVE-2017-20208](https://insights.sbomify.com/CVE-2017-20208/): RegistrationMagic - Custom Registration Forms <= 3.7.9.2 - PHP Object Injection (critical 9.8)
- [CVE-2024-10508](https://insights.sbomify.com/CVE-2024-10508/): Auth bypass in RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login (critical 9.8)
- [CVE-2021-4073](https://insights.sbomify.com/CVE-2021-4073/): RegistrationMagic <= 5.0.1.7 Authentication Bypass (critical 9.8)
- [CVE-2024-1990](https://insights.sbomify.com/CVE-2024-1990/): SQL injection in RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login (high 8.8)
- [CVE-2024-1991](https://insights.sbomify.com/CVE-2024-1991/): Privilege escalation in RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2499 and fix it if it is affected.

What it is: CVE-2023-2499 is a critical authentication bypass vulnerability in metagauss RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login, published on 16 May 2023. 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-2023-2499 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-2023-2499/ (Markdown: https://insights.sbomify.com/CVE-2023-2499/index.md)
```

## Sources

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

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