# CVE-2021-24862: RegistrationMagic < 5.0.1.6 - Admin+ SQL Injection

> An authenticated admin can exploit SQL injection in the RegistrationMagic plugin to read or modify database contents.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cr8f-vxv2-c345

## What is CVE-2021-24862?

CVE-2021-24862 is a high-severity SQL injection vulnerability in Unknown RegistrationMagic – Custom Registration Forms, User Registration and User Login Plugin, published on 10 Jan 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The RegistrationMagic WordPress plugin before 5.0.1.6 does not escape user input in its rm_chronos_ajax AJAX action before using it in a SQL statement when duplicating tasks in batches, which could lead to a SQL injection issue

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2021-24862?

It affects 1 product.


Products: Metagauss Registrationmagic.

## How do I fix CVE-2021-24862?

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

## Is CVE-2021-24862 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24862 exists.

Public exploit code:

- Wordpress RegistrationMagic task_ids Authenticated SQLi (metasploit)
- WordPress Plugin RegistrationMagic V 5.0.1.5 - SQL Injection (Authenticated) (exploitdb)
- WordPress RegistrationMagic <5.0.1.6 - Authenticated SQL Injection (nuclei): http/cves/2021/CVE-2021-24862.yaml

## Other vulnerabilities in Unknown RegistrationMagic – Custom Registration Forms, User Registration and User Login Plugin

- [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-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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24862 and fix it if it is affected.

What it is: CVE-2021-24862 is a high-severity SQL injection vulnerability in Unknown RegistrationMagic – Custom Registration Forms, User Registration and User Login Plugin, published on 10 Jan 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24862 exists.

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

## Sources

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

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