sales@hackhalt.com

Home / Threats / CVE-2024-9820

Two Factor Login Telegram - Authentication Bypass (CVE-2024-9820)

CVE-2024-9820

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.

CVE-2024-9820

MEDIUM CVSS 6.5 Published 2024-10-15 Updated 2026-06-17
AI Risk Elevated (70/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Affected Components 2
Reference Links 2
AI Risk Engine Elevated (70/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2024-10-15 CVE published and first recorded in the threat feed.
  2. 2026-06-17 Record updated with latest vulnerability metadata.
  3. 2026-04-09 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 217 days ago

AI enriched 217 days ago (2026-04-09 08:42 UTC)

Technical Summary

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.

Potential Impact

Severity is MEDIUM (CVSS 6.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Two Factor Login Telegram to 3.1 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Administrator multi-factor authentication in Hack Halt Pro blocks this class of attack before WordPress processes the request.

Require a second factor for every administrator account. This is the single highest-value control against credential stuffing and reused passwords, because a valid password alone stops being enough.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Two Factor Login Telegram, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Two Factor Login Telegram. Versions below 3.1 are vulnerable; that release and later are not. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update Two Factor Login Telegram to version 3.1 or later. That is the complete fix. Until you can update, Administrator multi-factor authentication in Hack Halt Pro contains this class of attack at the request layer.

What can an attacker actually do?

This is a Authentication Bypass flaw. An attacker who exploits it can sign in as another user, frequently an administrator, without a password.