# CVE-2024-0588: Paid Memberships Pro <= 2.12.10 - Cross-Site Request Forgery

> Unauthenticated attackers can trick administrators into enabling Lifter LMS streamline settings via forged requests in the Paid Memberships Pro plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Apr 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7p7p-r9pc-pcmf

## What is CVE-2024-0588?

CVE-2024-0588 is a medium-severity vulnerability in strangerstudios Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions, published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.12.10. This is due to missing nonce validation on the pmpro_lifter_save_streamline_option() function. This makes it possible for unauthenticated attackers to enable the streamline setting with Lifter LMS via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE-2024-32793 and CVE-2024-32794 appear to be a duplicate of this issue.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-0588?

It affects 1 product.


Products: Strangerstudios Paid Memberships Pro.

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

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

## Is CVE-2024-0588 being exploited?

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

Public exploit code:

- a PoC for CVE-2024-0588/WP Plugin - Paid Memberships Pro (<= 2.12.7) (github_poc): https://github.com/kodaichodai/CVE-2024-0588

## 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-2024-0588 and fix it if it is affected.

What it is: CVE-2024-0588 is a medium-severity vulnerability in strangerstudios Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions, published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-0588 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-2024-0588/ (Markdown: https://insights.sbomify.com/CVE-2024-0588/index.md)
```

## Sources

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

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