# CVE-2020-37169: WordPress Plugin ultimate-member 2.1.3 Local File Inclusion

> Authenticated attackers can exploit a local file inclusion vulnerability in the Ultimate Member plugin to execute arbitrary code via manipulated parameters.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-vm2q-f7mg-hvvh

## What is CVE-2020-37169?

CVE-2020-37169 is a medium-severity path traversal vulnerability in ultimate-member, published on 13 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WordPress Plugin ultimate-member 2.1.3 contains a local file inclusion vulnerability that allows authenticated attackers to include arbitrary files by manipulating the pack parameter in class-admin-upgrade.php. Attackers can send POST requests with malicious pack values to include unintended PHP files from the packages directory and execute arbitrary code.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2020-37169?


## How do I fix CVE-2020-37169?

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

## Is CVE-2020-37169 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37169 and fix it if it is affected.

What it is: CVE-2020-37169 is a medium-severity path traversal vulnerability in ultimate-member, published on 13 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37169 exists.

Affected product: ultimate-member. 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-2020-37169/ (Markdown: https://insights.sbomify.com/CVE-2020-37169/index.md)
```

## Sources

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

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