# CVE-2024-10508: Auth bypass in RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login

> Unauthenticated attackers can reset arbitrary user passwords, including administrators, due to improper token validation in the RegistrationMagic WordPress plugin.

- **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:** 9 Nov 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-vh3h-6j4p-c645

## What is CVE-2024-10508?

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

### Official description

The RegistrationMagic – User Registration Plugin with Custom Registration Forms plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 6.0.2.6. This is due to the plugin not properly validating the password reset token prior to updating a user's password. This makes it possible for unauthenticated attackers to reset the password of arbitrary users, including administrators, and gain access to these accounts.

Weakness: CWE-230 (Improper Handling of Missing Values)

## Which versions are affected by CVE-2024-10508?

It affects 1 product.


Products: Metagauss Registrationmagic.

## How do I fix CVE-2024-10508?

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

## Is CVE-2024-10508 being exploited?

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

Public exploit code:

- This tool scans WordPress sites for vulnerabilities in the "RegistrationMagic" plugin (CVE-2024-10508). It checks for the presence of a specific version (`6.0.2.6`) and marks the site as vulnerable if found. The results are saved in a file (`vuln.txt`) for further analysis. (github_poc): https://github.com/Jenderal92/CVE-2024-10508
- https://github.com/ubaydev/CVE-2024-10508 (github_poc): https://github.com/ubaydev/CVE-2024-10508

## 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-2023-2499](https://insights.sbomify.com/CVE-2023-2499/): RegistrationMagic <= 5.2.1.0 - Authentication Bypass (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-2024-10508 and fix it if it is affected.

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

## Sources

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

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