# CVE-2026-85659: PilotPress <= 2.0.43 - Authenticated (Subscriber+) Privilege Escalation via Account Takeover via 'username' Parameter

> Authenticated attackers can escalate privileges to Administrator by exploiting a race condition in the PilotPress plugin's account synchronization logic.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-ph8g-mcqh-5p98

## What is CVE-2026-85659?

CVE-2026-85659 is a high-severity vulnerability in ontraport PilotPress, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The PilotPress plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in all versions up to, and including, 2.0.43. The vulnerability exists because the `update_cc_details()` AJAX handler forwards an attacker-supplied `username` parameter to ONTRAPORT via `api_call('update_cc_details', ...)` before performing the local `username_exists()` collision check, and aborts without rolling back the remote rename when a collision is detected — leaving the remote ONTRAPORT contact renamed to an existing WordPress Administrator's login. On a subsequent login attempt, `user_login()` (hooked to `wp_authenticate`) authenticates against ONTRAPORT using the renamed login and the attacker's own password, resolves the local WordPress user row via `get_user_by('login', $username)` — which now selects the real Administrator's row — and calls `wp_set_password()` against that Administrator's user ID; because the `user_level != 10` guard only suppresses PilotPress's own cookie issuance rather than returning a `WP_Error` to core, WordPress proceeds to validate the newly-synchronized password and issues a full Administrator authentication cookie to the attacker. This makes it possible for authenticated attackers with Subscriber-level access and above — specifically any PilotPress member holding a valid ONTRAPORT contact and the Customer Center nonce — to fully take over an Administrator account.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-85659 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85659 is a high-severity vulnerability in ontraport PilotPress, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85659 in the wild and no public exploit code.

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

## Sources

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

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