Skip to content
Laskyr

CVE-2026-93757: Wild Apricot Login authentication bypass vulnerability

high 7.5 plugin closed published 2026-10-29

Wild Apricot Login is closed on wordpress.org, so no fix is coming through WordPress updates

Wild Apricot Login 1.0.18 and older is affected by this authentication bypass issue. The plugin was closed on wordpress.org on 2026-10-20, so sites running it will not be offered an update.

Affected versions
1.0.18 and older
Fixed in
unknown
Severity
High · CVSS 7.5
Active installs
closed
Type
Authentication bypass

What an attacker needs

CVSS vector (score by Wordfence): CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

What to do now

  1. Replace Wild Apricot Login. A closed plugin gets no updates through WordPress, so this hole stays open.
  2. Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deactivating alone leaves its files on the server.
  3. Not sure which version you run? Check your version against every known Wild Apricot Login issue.
  4. If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.

The advisory

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.

Description from the CVE record, published by Wordfence (the CVE Numbering Authority), via the NVD entry for CVE-2026-93757.

References

Related

Ran an affected version? Check your site for signs of a hack

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Already hacked? Flat $499 cleanup with a 30-day reinfection guarantee.

Where this data comes from

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit