# CVE-2023-6187: Paid Memberships Pro <= 2.12.3 - Authenticated (Subscriber+) Arbitrary File Upload

> Authenticated attackers can upload arbitrary files leading to remote code execution if specific payment methods and custom user fields are configured.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/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:** 18 Nov 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wwhh-cm65-x8qq

## What is CVE-2023-6187?

CVE-2023-6187 is a high-severity vulnerability in strangerstudios Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions, published on 18 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Paid Memberships Pro plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the 'pmpro_paypalexpress_session_vars_for_user_fields' function in versions up to, and including, 2.12.3. This makes it possible for authenticated attackers with subscriber privileges or above, to upload arbitrary files on the affected site's server which may make remote code execution possible. This can be exploited if 2Checkout (deprecated since version 2.6) or PayPal Express is set as the payment method and a custom user field is added that is only visible at profile, and not visible at checkout according to its settings.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2023-6187?

It affects 1 product.


Products: Strangerstudios Paid Memberships Pro.

## How do I fix CVE-2023-6187?

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

## Is CVE-2023-6187 being exploited?

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

## Other vulnerabilities in strangerstudios Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions

- [CVE-2023-23488](https://insights.sbomify.com/CVE-2023-23488/): SQL injection in Paid Memberships Pro WordPress Plugin (critical 9.8)
- [CVE-2021-25114](https://insights.sbomify.com/CVE-2021-25114/): Paid Memberships Pro < 2.6.7 - Unauthenticated Blind SQL Injection (critical 9.8)
- [CVE-2023-0631](https://insights.sbomify.com/CVE-2023-0631/): Paid Memberships Pro < 2.9.12 - Subscriber+ SQL Injection (high 8.8)
- [CVE-2021-20678](https://insights.sbomify.com/CVE-2021-20678/): SQL injection in Paid Memberships Pro (high 8.8)
- [CVE-2024-37486](https://insights.sbomify.com/CVE-2024-37486/): WordPress Paid Memberships Pro plugin <= 3.0.5 - Authenticated SQL Injection vulnerability (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6187 and fix it if it is affected.

What it is: CVE-2023-6187 is a high-severity vulnerability in strangerstudios Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions, published on 18 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6187 in the wild and no public exploit code.

Affected product: strangerstudios Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions. 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-2023-6187/ (Markdown: https://insights.sbomify.com/CVE-2023-6187/index.md)
```

## Sources

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

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