# CVE-2025-13587: Two Factor (2FA) Authentication via Email <= 1.9.8 - Two-Factor Authentication Bypass via token

> Attackers can bypass two-factor authentication in the Two Factor (2FA) Authentication via Email WordPress plugin by supplying a token parameter during login.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 19 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-87q3-cqqr-mvcg

## What is CVE-2025-13587?

CVE-2025-13587 is a medium-severity authentication bypass vulnerability in ss88_uk Two Factor (2FA) Authentication via Email, published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Two Factor (2FA) Authentication via Email plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions up to, and including, 1.9.8. This is because the SS88_2FAVE::wp_login() method only enforces the 2FA requirement if the 'token' HTTP GET parameter is undefined, which makes it possible to bypass two-factor authentication by supplying any value in the 'token' parameter during login, including an empty one.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-13587?


## How do I fix CVE-2025-13587?

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

## Is CVE-2025-13587 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13587 and fix it if it is affected.

What it is: CVE-2025-13587 is a medium-severity authentication bypass vulnerability in ss88_uk Two Factor (2FA) Authentication via Email, published on 19 Feb 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-2025-13587 in the wild and no public exploit code.

Affected product: ss88_uk Two Factor (2FA) Authentication via Email. 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-2025-13587/ (Markdown: https://insights.sbomify.com/CVE-2025-13587/index.md)
```

## Sources

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

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