dbcve.org
Wp 2fa With TelegramWordPress extension · Dueclic

CVE-2024-9820

HIGH · 7.5 CVSS v3.1 Published 2024-10-15
Fix available
A fix is available. Upgrade to 3.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP 2FA with Telegram plugin for WordPress versions up to 3.0 stores the two-factor authentication code in a cookie, allowing attackers to potentially intercept or manipulate this cookie to bypass the two-factor authentication mechanism entirely.

MitigationUpdate the plugin to a version that implements session-based or server-side validation instead of cookie-based storage for 2FA codes, and rotate any potentially compromised credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp 2fa With TelegramWordPress extension
Affected:< 3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'WP 2FA with Telegram' or 'Dueclic Wp 2fa With Telegram' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'wp-2fa-telegram' or similar.
    Affected if The plugin is not found in the installed plugins list or the plugins directory.
  2. Check installed version number
    In WordPress admin, find the plugin in the plugins list and note the version number displayed beneath the plugin name. Compare this against the affected range of versions < 3.1.
    Affected if The installed version is any version prior to 3.1 (e.g., 3.0, 2.9, 1.x).
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the plugin shows as 'Active' rather than 'Inactive' or 'Must Use'. The vulnerability only applies to an active, functioning installation.
    Affected if The plugin is activated and processing 2FA authentication requests.
  4. Inspect browser cookies during 2FA flow
    During a login attempt that triggers 2FA, open browser developer tools (F12), go to Application > Cookies, and examine cookies set by the site. Look for any cookie that appears to contain a numeric or alphanumeric code used for 2FA validation.
    Affected if A cookie containing the 2FA code is stored in the browser rather than validated server-side only.

You are affected if the WP 2FA with Telegram plugin is active and the installed version is any version before 3.1, as these versions store the authentication code in a client-side cookie.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1 or later
Fixed in 3.1
Interim mitigation

Update the plugin to a version that implements session-based or server-side validation instead of cookie-based storage for 2FA codes, and rotate any potentially compromised credentials.

Recommended fix High confidence

3.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WP 2FA with Telegram' plugin
  4. Check if the current version is below 3.1
  5. If below 3.1, click 'Update Now' to update to version 3.1
  6. Alternatively, navigate to Dashboard > Updates and update the plugin from there
  7. Verify the update was successful by confirming the plugin now shows version 3.1 or higher
  8. Test the two-factor authentication to confirm it is functioning properly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp 2fa With Telegram Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9820 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9820 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data