https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Mon, 04 May 2026 14:37:24 +0000 https://db.gcve.eu/sighting/2a71a0aa-cb59-46f9-a89c-c8bbc22f6b32/export {"uuid": "2a71a0aa-cb59-46f9-a89c-c8bbc22f6b32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1717", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/114075218651181708", "content": "", "creation_timestamp": "2025-02-27T09:48:19.245597Z"} {"uuid": "2a71a0aa-cb59-46f9-a89c-c8bbc22f6b32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1717", "type": "seen", "source": "https://mastodon.social/users/CyberSignaler/statuses/114075218651181708", "content": "", "creation_timestamp": "2025-02-27T09:48:19.245597Z"} https://db.gcve.eu/sighting/2a71a0aa-cb59-46f9-a89c-c8bbc22f6b32/export Thu, 27 Feb 2025 09:48:19 +0000 https://db.gcve.eu/sighting/f93f01e7-a28c-4477-a1b7-d1676280bdd0/export {"uuid": "f93f01e7-a28c-4477-a1b7-d1676280bdd0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1717", "type": "seen", "source": "https://t.me/cvedetector/19026", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-1717 - WordPress Login Me Now Plugin Authentication Bypass\", \n \"Content\": \"CVE ID : CVE-2025-1717 \nPublished : Feb. 27, 2025, 8:15 a.m. | 1\u00a0hour, 3\u00a0minutes ago \nDescription : The Login Me Now plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.7.2. This is due to insecure authentication based on an arbitrary transient name in the 'AutoLogin::listen()' function. This makes it possible for unauthenticated attackers to log in an existing user on the site, even an administrator. Note: this vulnerability requires using a transient name and value from another software, so the plugin is not inherently vulnerable on it's own. \nSeverity: 8.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Feb 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T10:22:16.000000Z"} {"uuid": "f93f01e7-a28c-4477-a1b7-d1676280bdd0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1717", "type": "seen", "source": "https://t.me/cvedetector/19026", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-1717 - WordPress Login Me Now Plugin Authentication Bypass\", \n \"Content\": \"CVE ID : CVE-2025-1717 \nPublished : Feb. 27, 2025, 8:15 a.m. | 1\u00a0hour, 3\u00a0minutes ago \nDescription : The Login Me Now plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.7.2. This is due to insecure authentication based on an arbitrary transient name in the 'AutoLogin::listen()' function. This makes it possible for unauthenticated attackers to log in an existing user on the site, even an administrator. Note: this vulnerability requires using a transient name and value from another software, so the plugin is not inherently vulnerable on it's own. \nSeverity: 8.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"27 Feb 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-27T10:22:16.000000Z"} https://db.gcve.eu/sighting/f93f01e7-a28c-4477-a1b7-d1676280bdd0/export Thu, 27 Feb 2025 10:22:16 +0000 https://db.gcve.eu/sighting/d0348555-d080-4807-b77e-d378e95a2b0e/export {"uuid": "d0348555-d080-4807-b77e-d378e95a2b0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1717", "type": "seen", "source": "Telegram/u5U5HkdsjVTNTjKDjqO60RM8YSduevD2fdfzdqTTMF2XVOk", "content": "", "creation_timestamp": "2025-02-27T11:00:55.000000Z"} {"uuid": "d0348555-d080-4807-b77e-d378e95a2b0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1717", "type": "seen", "source": "Telegram/u5U5HkdsjVTNTjKDjqO60RM8YSduevD2fdfzdqTTMF2XVOk", "content": "", "creation_timestamp": "2025-02-27T11:00:55.000000Z"} https://db.gcve.eu/sighting/d0348555-d080-4807-b77e-d378e95a2b0e/export Thu, 27 Feb 2025 11:00:55 +0000 https://db.gcve.eu/sighting/8dba1304-26b1-49e8-8935-6fe2b25eb522/export {"uuid": "8dba1304-26b1-49e8-8935-6fe2b25eb522", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1717", "type": "seen", "source": "Telegram/cGa8yDyNVwYsWwQDKbAEW9iF4JktgxdPCEl6-1qKx7qpCzI", "content": "", "creation_timestamp": "2026-04-08T23:29:45.000000Z"} {"uuid": "8dba1304-26b1-49e8-8935-6fe2b25eb522", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1717", "type": "seen", "source": "Telegram/cGa8yDyNVwYsWwQDKbAEW9iF4JktgxdPCEl6-1qKx7qpCzI", "content": "", "creation_timestamp": "2026-04-08T23:29:45.000000Z"} https://db.gcve.eu/sighting/8dba1304-26b1-49e8-8935-6fe2b25eb522/export Wed, 08 Apr 2026 23:29:45 +0000