CVE-2026-93757
HIGHDescription
The Wild Apricot Login plugin for WordPress is vulnerable to Authentication Bypass via SSO Email-Collision Account Binding in all versions up to, and including, 1.0.18. When no WildApricot contact-ID mapping is found for an incoming SSO login, the plugin falls back to a network-global `get_user_by('email', ...)` lookup in `Module.php` to resolve a WordPress user, then `UserSynchronizer::syncWaContact()` binds and `Controller::login()` issues a session cookie via `wp_set_auth_cookie()` for that resolved user — both guarded only by `is_super_admin()` — without ever requiring proof of ownership of the matched WordPress account such as a password, local account-linking confirmation, inbox verification, or administrator approval. This makes it possible for attackers with custom-level WildApricot membership access to authenticate as an existing WordPress subsite administrator on a path-based Multisite network, obtaining a valid network-global authentication cookie for the victim without their credentials. Exploitation requires that the attacker control a WildApricot contact whose email address matches the target WordPress administrator's email — achievable via a public zero-fee membership application on the connected WildApricot organization — and that they complete the SSO flow on any subsite where Wild Apricot Login is active; because WordPress user identities and authentication cookies are network-global, the cookie issued on that subsite is equally valid on any other subsite where the victim user holds an administrator role.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 37% of all known CVEs.
References
Related Vulnerabilities
Other CWE-287 (Improper Authentication) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-7593 | Critical | 9.8 | 100% | KEV | - |
| CVE-2023-35082 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2023-35078 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2017-7921 | Critical | 9.8 | 100% | KEV | - |
| CVE-2021-33044 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2023-46805 | High | 8.2 | 100% | KEV + Ransom | - |
Common questions
How do I fix CVE-2026-93757?
No published fix for CVE-2026-93757 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-93757 being actively exploited?
Not that we know of. CVE-2026-93757 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.43% is the estimated probability that it will be exploited in the next 30 days. That is higher than 37% of all scored CVEs.
How severe is CVE-2026-93757?
CVE-2026-93757 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-93757
Markdown
[](https://tridentstack.com/cve/CVE-2026-93757)HTML
<a href="https://tridentstack.com/cve/CVE-2026-93757"><img src="https://tridentstack.com/cve/badge/CVE-2026-93757.svg" alt="CVE-2026-93757"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-29.