https://vulnerability.circl.lu/sightings/feed 2026-05-09T11:22:03.984838+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/10166700-27f8-4d4b-a61d-eb77c06addd1/export 2026-05-09T11:22:04.341869+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "10166700-27f8-4d4b-a61d-eb77c06addd1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-9687", "type": "seen", "source": "https://t.me/cvedetector/7877", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-9687 - WordPress WP 2FA with Telegram Authentication Bypass\", \n \"Content\": \"CVE ID : CVE-2024-9687 \nPublished : Oct. 15, 2024, 2:15 a.m. | 41\u00a0minutes ago \nDescription : 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. \nSeverity: 8.8 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"15 Oct 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-15T05:13:44.000000Z"} 2024-10-15T05:13:44+00:00