WP 2FA with Telegram <= 3.0 - Authenticated (Subscriber+) Authentication Bypass
Priority MEDIUM 41CWE-639Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
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.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00482 41st 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
- Total
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-9687
- 2026-10-03 Alias added: GHSA-rfxp-9x8m-jfw8
References
More dueclic Wp 2fa With Telegram vulnerabilities
- TI-2024-09113 WP 2FA with Telegram <= 3.0 - Two-Factor Authentication Bypass CVSS 3.1HIGH 7.5
Sources
- CVE-2024-9687 · CVE Program
- CVE-2024-9687 · NVD
- FIRST EPSS
- GHSA-rfxp-9x8m-jfw8 · 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