# CVE-2022-3361: Path traversal in Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin

> Authenticated attackers can exploit directory traversal in Ultimate Member plugin to read arbitrary files or potentially execute code via file inclusion.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 29 Nov 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q6cc-3x9h-cxmm

## What is CVE-2022-3361?

CVE-2022-3361 is a medium-severity path traversal vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin, published on 29 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Ultimate Member plugin for WordPress is vulnerable to directory traversal in versions up to, and including 2.5.0 due to insufficient input validation on the 'template' attribute used in shortcodes. This makes it possible for attackers with administrative privileges to supply arbitrary paths using traversal (../../) to access and include files outside of the intended directory. If an attacker can successfully upload a php file then remote code execution via inclusion may also be possible. Note: for users with less than administrative capabilities, /wp-admin access needs to be enabled for that user in order for this to be exploitable by those users.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Ultimatemember Ultimate Member.

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

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

## Is CVE-2022-3361 being exploited?

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

What it is: CVE-2022-3361 is a medium-severity path traversal vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin, published on 29 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3361 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-3361/ (Markdown: https://insights.sbomify.com/CVE-2022-3361/index.md)
```

## Sources

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

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