# CVE-2022-3384: Code injection in Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin

> Authenticated administrators can execute arbitrary code on the server via a vulnerable function in the Ultimate Member WordPress plugin.

- **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:** 29 Nov 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-3x6p-668f-f973

## What is CVE-2022-3384?

CVE-2022-3384 is a high-severity code injection vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin, published on 29 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Ultimate Member plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 2.5.0 via the populate_dropdown_options function that accepts user supplied input and passes it through call_user_func(). This is restricted to non-parameter PHP functions like phpinfo(); since user supplied parameters are not passed through the function. This makes it possible for authenticated attackers, with administrative privileges, to execute code on the server.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-3384?

It affects 1 product.


Products: Ultimatemember Ultimate Member.

## How do I fix CVE-2022-3384?

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

## Is CVE-2022-3384 being exploited?

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

## 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-2024-1071](https://insights.sbomify.com/CVE-2024-1071/): SQL injection in Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin (critical 9.8)
- [CVE-2023-3460](https://insights.sbomify.com/CVE-2023-3460/): Ultimate Member < 2.6.7 - Unauthenticated Privilege Escalation (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3384 and fix it if it is affected.

What it is: CVE-2022-3384 is a high-severity code injection vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin, published on 29 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3384 in the wild and no public exploit code.

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-2022-3384/ (Markdown: https://insights.sbomify.com/CVE-2022-3384/index.md)
```

## Sources

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

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