CVE-2024-9820: The WP 2FA with Telegram plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions up

Q: How do I fix CVE-2024-9820?

wp 2fa with telegram: upgrade to 3.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-9820 being exploited?

CVE-2024-9820 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-9820 affect?

CVE-2024-9820 affects wp 2fa with telegram. Severity is medium (CVSS 6.5). The WP 2FA with Telegram plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions up to, and including, 3.0. This is due to the two-factor code being stored in a cookie, which makes it possible to bypass two-factor

Q: How urgent is CVE-2024-9820?

Priority 31/100. No elevated risk signals yet.

Routine

MEDIUM 6.5UPGRADE

CVE-2024-9820 is a medium-severity flaw (CVSS 6.5) affecting wp 2fa with telegram. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP 2FA with Telegram plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions up to, and including, 3.0. This is due to the two-factor code being stored in a cookie, which makes it possible to bypass two-factor authentication.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-784, CWE-565
Published	2024-10-15
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: dueclic

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-10-15 02:15 UTCPublished CVE record published
2026-06-17 08:25 UTCUpdated Record last modified

dueclic wp 2fa with telegram UPGRADE

Affected: < 3.1

Fixed in: 3.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-2fa-with-telegram || rpm -q wp-2fa-with-telegram || wp-2fa-with-telegram --version

2. UPGRADE to 3.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-2fa-with-telegram

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-2fa-with-telegram

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-9820?

wp 2fa with telegram: upgrade to 3.1. Exact commands for each OS are on this page.

Is CVE-2024-9820 being exploited?

CVE-2024-9820 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-9820 affect?

CVE-2024-9820 affects wp 2fa with telegram. Severity is medium (CVSS 6.5). The WP 2FA with Telegram plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions up to, and including, 3.0. This is due to the two-factor code being stored in a cookie, which makes it possible to bypass two-factor

How urgent is CVE-2024-9820?

Priority 31/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities · Telegram vulnerabilities

Related CVEs

CVE-2024-9687 HIGH 8.8 UPGRADE The WP 2FA with Telegram plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and in

References

← Back to latest CVEs