# CVE-2026-88785: Simple Membership < 4.8.3 - Newly Registered Member Password Disclosure via URL Query String

> Attackers can read plaintext passwords from logs or history if auto-login is enabled, exposing user credentials.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-vv5r-wf9f-5j7m

## What is CVE-2026-88785?

CVE-2026-88785 is a medium-severity vulnerability in Unknown Simple Membership, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Simple Membership WordPress plugin before 4.8.3 does not avoid transmitting a newly registered member's plaintext password in a URL query string when an optional auto-login-after-registration feature is enabled, exposing the credential in browser history and in web server, proxy, and CDN access logs to anyone able to read them.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-88785 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88785 is a medium-severity vulnerability in Unknown Simple Membership, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88785 in the wild and no public exploit code.

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

## Sources

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

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