https://db.gcve.eu/sightings/feed 2026-05-01T08:09:32.770878+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent sightings. https://db.gcve.eu/sighting/317a326a-84ca-4be5-9571-23ef253365d7/export 2026-05-01T08:09:33.117558+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "317a326a-84ca-4be5-9571-23ef253365d7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-9649", "type": "seen", "source": "https://t.me/cvedetector/7994", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-9649 - WordPress WP ULike CSRF vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-9649 \nPublished : Oct. 16, 2024, 2:15 a.m. | 44\u00a0minutes ago \nDescription : The WP ULike \u2013 The Ultimate Engagement Toolkit for Websites plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.7.4. This is due to missing or incorrect nonce validation on the wp_ulike_delete_history_api() function. This makes it possible for unauthenticated attackers to delete engagements via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. \nSeverity: 4.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Oct 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-16T05:29:19.000000Z"} 2024-10-16T05:29:19+00:00