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


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-j3xg-qwqj-hq74

## What is CVE-2026-93757?

CVE-2026-93757 is a high-severity vulnerability in wild-apricot Wild Apricot Login, published on 29 Oct 2026. 

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-93757?


## How do I fix CVE-2026-93757?

No fix has been published for CVE-2026-93757 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93757 being exploited?

There is no known exploitation of CVE-2026-93757 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93757 and fix it if it is affected.

What it is: CVE-2026-93757 is a high-severity vulnerability in wild-apricot Wild Apricot Login, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-93757 in the wild and no public exploit code.

Affected product: wild-apricot Wild Apricot Login. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93757/ (Markdown: https://insights.sbomify.com/CVE-2026-93757/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93757
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93757
- OSV: https://osv.dev/vulnerability/CVE-2026-93757

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93757/
Summaries are generated and may contain mistakes; the official description above is the record.