# CVE-2024-1071: SQL injection in Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin

> Unauthenticated attackers can exploit SQL injection in the Ultimate Member plugin to extract sensitive database information.

- **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:** 13 Mar 2024
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-mh7h-gpmx-fggj

## What is CVE-2024-1071?

CVE-2024-1071 is a critical SQL injection vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to SQL Injection via the 'sorting' parameter in versions 2.1.3 to 2.8.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for unauthenticated attackers 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-1071?

It affects 1 product.


Products: Ultimatemember Ultimate Member.

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

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

## Is CVE-2024-1071 being exploited?

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

Public exploit code:

- Proof of concept : CVE-2024-1071: WordPress Vulnerability Exploited (github_poc): https://github.com/gh-ost00/CVE-2024-1071-SQL-Injection
- Ultimate Member Unauthorized Database Access / SQLi (github_poc): https://github.com/gbrsh/CVE-2024-1071
- CVE-2024-1071 with Docker (github_poc): https://github.com/Trackflaw/CVE-2024-1071-Docker
- https://github.com/dogucyber/WordPress-Exploit-CVE-2024-1071 (github_poc): https://github.com/dogucyber/WordPress-Exploit-CVE-2024-1071
- wp/ultimate-member  -  SQL Injection Vulnerability Exploit Script. (github_poc): https://github.com/Spid3heX/CVE-2024-1071-PoC-Script
- CVE-2024-1071 (github_poc): https://github.com/Matrexdz/CVE-2024-1071

## Other vulnerabilities in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin

- [CVE-2020-36155](https://insights.sbomify.com/CVE-2020-36155/): Privilege escalation in n/a (critical 10.0)
- [CVE-2020-36157](https://insights.sbomify.com/CVE-2020-36157/): Privilege escalation in n/a (critical 10.0)
- [CVE-2020-36156](https://insights.sbomify.com/CVE-2020-36156/): Privilege escalation in n/a (critical 9.9)
- [CVE-2023-3460](https://insights.sbomify.com/CVE-2023-3460/): Ultimate Member < 2.6.7 - Unauthenticated Privilege Escalation (critical 9.8)
- [CVE-2019-10270](https://insights.sbomify.com/CVE-2019-10270/): Auth bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1071 and fix it if it is affected.

What it is: CVE-2024-1071 is a critical SQL injection vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1071 exists.

Affected product: ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership 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-2024-1071/ (Markdown: https://insights.sbomify.com/CVE-2024-1071/index.md)
```

## Sources

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

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