CVE-2026-85659: PilotPress <= 2.0.43 - Authenticated (Subscriber+) Privilege Escalation via Account Takeover via 'username' Parameter
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 updateccdetails() AJAX handler forwards an attacker-supplied username parameter to ONTRAPORT via apicall('updateccdetails', ...) before performing the local usernameexists() 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, userlogin() (hooked to wpauthenticate) authenticates against ONTRAPORT using the renamed login and the attacker's own password, resolves the local WordPress user row via getuserby('login', $username) — which now selects the real Administrator's row — and calls wpsetpassword() against that Administrator's user ID; because the userlevel != 10 guard only suppresses PilotPress's own cookie issuance rather than returning a WPError 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.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed?
PilotPress versions up to and including 2.0.43 are affected. Exploitation depends on the plugin using its ONTRAPORT-backed account update and authentication flows.
What access does an attacker need to exploit this issue?
An attacker needs an authenticated WordPress account with at least Subscriber-level access. They can supply a username value through the update_cc_details() AJAX handler and use their own password during the subsequent login flow.
What conditions enable the administrator takeover?
The attacker must target the login name of an existing WordPress Administrator. The vulnerable flow renames the attacker-controlled ONTRAPORT contact to that existing login, then associates the later authentication and password synchronization with the Administrator's local WordPress user record.
How can an organization identify a possible exploitation attempt?
Look for ONTRAPORT contact rename activity that changes a non-administrator contact's login or username to the login of an existing WordPress Administrator. A subsequent login using that username with the original lower-privileged user's password is indicative of the described attack path.