# CVE-2026-19709: Membership For WooCommerce < 3.1.2 - Unauthenticated Member Data Disclosure via REST Consumer Secret Bypass

> Unauthenticated attackers can bypass API authentication to disclose user membership details if the API is enabled but keys are not generated.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 19 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-5c3c-g52p-xg2h

## What is CVE-2026-19709?

CVE-2026-19709 is a medium-severity authentication bypass vulnerability in Unknown Membership For WooCommerce, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Membership For WooCommerce WordPress plugin before 3.1.2 does not check that an API consumer secret has actually been generated before comparing it against the one supplied in a request, allowing unauthenticated attackers to reach its REST routes and disclose any user's membership plan details on sites where the API has been enabled but no keys were ever generated.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-19709 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19709 is a medium-severity authentication bypass vulnerability in Unknown Membership For WooCommerce, published on 19 Aug 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-19709 in the wild and no public exploit code.

Affected product: Unknown Membership For WooCommerce. 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-19709/ (Markdown: https://insights.sbomify.com/CVE-2026-19709/index.md)
```

## Sources

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

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