# CVE-2026-86814: UsersWP - Social Login < 1.5.10 - Unauthenticated Account Takeover via Unverified Provider Email

> Unauthenticated attackers can take over any user account, including administrators, by asserting their email through a social login provider.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-cg9c-x648-j6c7

## What is CVE-2026-86814?

CVE-2026-86814 is a high-severity authentication bypass vulnerability in Unknown UsersWP, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The UsersWP  WordPress plugin before 1.5.10 does not verify that a social login provider has confirmed ownership of an email address before using it to resolve an existing account, allowing unauthenticated attackers to log in as any user, including administrators, whose email address they can assert through a provider account of their own.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-86814 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86814 is a high-severity authentication bypass vulnerability in Unknown UsersWP, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86814 in the wild and no public exploit code.

Affected product: Unknown UsersWP. 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-86814/ (Markdown: https://insights.sbomify.com/CVE-2026-86814/index.md)
```

## Sources

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

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