# CVE-2026-59539: WordPress Paid Member Subscriptions plugin <= 3.0.7 - Insecure Direct Object References (IDOR) vulnerability

> Subscribers can access or modify other users' data due to missing authorization checks in the Paid Member Subscriptions plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-vfqc-mpfj-gp23

## What is CVE-2026-59539?

CVE-2026-59539 is a high-severity missing authorization vulnerability in Cozmoslabs Paid Member Subscriptions, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Subscriber Insecure Direct Object References (IDOR) in Paid Member Subscriptions <= 3.0.7 versions.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-59539?


## How do I fix CVE-2026-59539?

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

## Is CVE-2026-59539 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59539 and fix it if it is affected.

What it is: CVE-2026-59539 is a high-severity missing authorization vulnerability in Cozmoslabs Paid Member Subscriptions, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59539 in the wild and no public exploit code.

Affected product: Cozmoslabs Paid Member 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-2026-59539/ (Markdown: https://insights.sbomify.com/CVE-2026-59539/index.md)
```

## Sources

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

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