# CVE-2024-9687: WP 2FA with Telegram <= 3.0 - Authenticated (Subscriber+) Authentication Bypass

> Authenticated subscribers can bypass two-factor authentication to log in as any user, including administrators, due to insufficient key validation.

- **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:** 15 Oct 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rfxp-9x8m-jfw8

## What is CVE-2024-9687?

CVE-2024-9687 is a high-severity authentication bypass vulnerability in dueclic AuthPress, published on 15 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP 2FA with Telegram plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 3.0. This is due to insufficient validation of the user-controlled key on the 'validate_tg' action. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to log in as any existing user on the site, such as an administrator.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2024-9687?

It affects 1 product.


Products: Dueclic Wp 2fa With Telegram.

## How do I fix CVE-2024-9687?

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

## Is CVE-2024-9687 being exploited?

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

## Other vulnerabilities in dueclic AuthPress

- [CVE-2024-9820](https://insights.sbomify.com/CVE-2024-9820/): WP 2FA with Telegram <= 3.0 - Two-Factor Authentication Bypass (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9687 and fix it if it is affected.

What it is: CVE-2024-9687 is a high-severity authentication bypass vulnerability in dueclic AuthPress, published on 15 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-9687 in the wild and no public exploit code.

Affected product: dueclic AuthPress. 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-2024-9687/ (Markdown: https://insights.sbomify.com/CVE-2024-9687/index.md)
```

## Sources

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

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