# CVE-2026-12595: LoginPress Pro <= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email via Discord OAuth Callback

> Unauthenticated attackers can take over any WordPress account, including administrators, by exploiting unverified Discord OAuth email validation in LoginPress Pro.

- **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:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-m2h5-jwrw-x8mr

## What is CVE-2026-12595?

CVE-2026-12595 is a high-severity authentication bypass vulnerability in LoginPress Pro, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The LoginPress Pro plugin for WordPress is vulnerable to Authentication Bypass via Unverified OAuth Email in all versions up to and including 6.2.3. The vulnerability exists in the loginpress_on_discord_login() Discord OAuth callback handler, which accepts the email field returned by Discord's /users/@me endpoint without ever checking that the profile's verified flag is true, then directly maps that email to a local WordPress account via get_user_by('email', $profile['email']) and issues an authenticated session cookie via wp_set_auth_cookie(). This makes it possible for unauthenticated attackers to take over any existing WordPress account — including administrator accounts — by registering a Discord account configured with an unverified email address that matches the target user's registered WordPress email and completing the standard Discord OAuth flow.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-12595 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12595 is a high-severity authentication bypass vulnerability in LoginPress Pro, published on 9 Jul 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-12595 in the wild and no public exploit code.

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

## Sources

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

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