WP 2FA with Telegram <= 3.0 - Two-Factor Authentication Bypass
Priority LOW 33CWE-784Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA.
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.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00402 34th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2024-9820
- 2026-10-03 Alias added: GHSA-x23h-whff-jxq7
References
More dueclic Wp 2fa With Telegram vulnerabilities
- TI-2024-08988 WP 2FA with Telegram <= 3.0 - Authenticated (Subscriber+) Authentication Bypass CVSS 3.1HIGH 8.8
Sources
- CVE-2024-9820 · CVE Program
- CVE-2024-9820 · NVD
- FIRST EPSS
- GHSA-x23h-whff-jxq7 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences