# CVE-2026-92797: Memberpress <= 1.14.1 - Cross-Site Request Forgery via 'user_email' Parameter


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-wc55-5qpx-prwh

## What is CVE-2026-92797?

CVE-2026-92797 is a high-severity vulnerability in Memberpress, published on 28 Oct 2026. 

### Official description

The MemberPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.14.1. This is due to a bypassable nonce verification check in the save_profile_fields() function that uses an isset() condition at line 1119, allowing the security check to be completely bypassed by simply omitting the nonce parameter from the request. This makes it possible for unauthenticated attackers to change authenticated users' email addresses via a forged request granted they can trick an authenticated user into performing an action such as clicking on a link, leading to account takeover through password reset functionality.

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

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


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

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

## Is CVE-2026-92797 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92797 is a high-severity vulnerability in Memberpress, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92797 in the wild and no public exploit code.

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

## Sources

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

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