# CVE-2026-14495: Auth bypass in DoLogin Security

> An unauthenticated attacker can brute-force weak passwordless login tokens to bypass authentication and gain administrator access in the DoLogin Security plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-3585-g468-xfc2

## What is CVE-2026-14495?

CVE-2026-14495 is a high-severity authentication bypass vulnerability in wpdo5ea DoLogin Security, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The DoLogin Security plugin for WordPress is vulnerable to Authentication Bypass via Insufficient Randomness in all versions up to, and including, 4.3. The vulnerability exists because `dologin\s::rrand()` seeds the Mersenne Twister with `mt_srand((double) microtime() * 1000000)` — discarding the integer-seconds component of `microtime()` and constraining the seed to a range of approximately 10^6 values (~20 bits of entropy) — after which every character of the 32-character magic-link token is drawn sequentially with `mt_rand()`, making the entire token a deterministic function of that seed. Because `Pswdless::try_login()` is registered on the unauthenticated `init` hook, resolves the target account by the auto-increment numeric ID embedded in the `?dologin=<id>.<hash>` parameter, performs the hash comparison using a non-constant-time `!=` operator, and then calls `wp_set_auth_cookie()` directly — never passing through `wp_authenticate()` and therefore never triggering the plugin's own `Auth::_has_login_err()` lockout — an unauthenticated attacker can brute-force the ~10^6-candidate seed space to reconstruct an active passwordless login token and authenticate as any targeted user, including administrators, without a password. Exploitation requires that a valid, unexpired passwordless login link (active for up to 7 days) exists for the target account at the time of the attack, and that the numeric link ID is known or guessable from the auto-increment primary key.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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


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

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

## Is CVE-2026-14495 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14495 is a high-severity authentication bypass vulnerability in wpdo5ea DoLogin Security, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14495 in the wild and no public exploit code.

Affected product: wpdo5ea DoLogin Security. 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-14495/ (Markdown: https://insights.sbomify.com/CVE-2026-14495/index.md)
```

## Sources

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

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