# CVE-2024-1990: SQL injection in RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login

> Authenticated contributors can exploit SQL injection in the RegistrationMagic plugin to extract sensitive database information.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-33m3-hvgx-q2v6

## What is CVE-2024-1990?

CVE-2024-1990 is a high-severity SQL injection vulnerability in metagauss RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to blind SQL Injection via the ‘id’ parameter of the RM_Form shortcode in all versions up to, and including, 5.3.1.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

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

It affects 1 product.


Products: Metagauss Registrationmagic.

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

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

## Is CVE-2024-1990 being exploited?

There is no known exploitation of CVE-2024-1990 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-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-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-1990 and fix it if it is affected.

What it is: CVE-2024-1990 is a high-severity SQL injection vulnerability in metagauss RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1990 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-1990/ (Markdown: https://insights.sbomify.com/CVE-2024-1990/index.md)
```

## Sources

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

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