Vulnerability · CVE-2026-85659
The PilotPress plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in all versions up to, and including, 2.0.43.
Published Oct 16, 2026 · catalog updated Oct 16, 2026 · The PilotPress plugin for
Check if you run it
No confirmed exploitation is on record for CVE-2026-85659. EPSS is 0.37%. Act only if a listed version of The PilotPress plugin for is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (The PilotPress plugin for).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High8.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.37%
- Remediation
- Version ranges on file
- Affected products
- stated named in the record
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 AJAX handler forwards an attacker-supplied parameter to ONTRAPORT via before performing the local 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, (hooked to ) authenticates against ONTRAPORT using the renamed login and the attacker's own password, resolves the local WordPress user row via — which now selects the real Administrator's row — and calls against that Administrator's user ID; because the guard only suppresses PilotPress's own cookie issuance rather than returning a 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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- stated named in the record<= 2.0.43
How to fix CVE-2026-85659
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-85659. EPSS is 0.37%. Act only if a listed version of The PilotPress plugin for is installed.
Which versions are affected?
Compare what you have installed with named in the record <= 2.0.43. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-269: Improper Privilege Management. EPSS 0.37%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 16, 2026 · NIST NVD
Detected
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 AJAX handler forwards an attacker-supplied parameter to ONTRAPORT via before performing the local collision check, and aborts without rolling back the remote rename when a collision is detected — leaving the remote ONTRAPO
Sources
- CVE.orgVulnerability recordCVE-2026-85659
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-85659
30-day exploitation probability 0.4%
first.org - NIST NVDVulnerability recordCVE-2026-85659
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 AJAX handler forwards an attacker-supplied parameter to ONTRAPORT via
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.