{"api_version":"v1","generated_at":"2026-10-08T22:05:00+00:00","product":{"cve_count":6,"evidence_gap_note":"This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.","id":"security:cve-rainafarai-notification-for-telegram-b15c5b33e062","lifecycle_state":"evidence_gap","linked_lifecycle_url":null,"name":"Notification for Telegram","next_cursor":null,"observations":[{"affected":"Notification for Telegram: n/a \u2264 3.5.2","affected_versions_present":true,"cve_id":"CVE-2026-93514","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-93514","fixed":"Update the WordPress Notification for Telegram Plugin to the latest available version (at least 3.5.3).","last_modified":"2026-09-30T13:17:01.912Z","patch_url":"https://patchstack.com/database/wordpress/plugin/notification-for-telegram/vulnerability/wordpress-notification-for-telegram-plugin-3-5-2-cross-site-scripting-xss-vulnerability?_s_id=cve","primary_source":"","published":"2026-09-30T12:26:52.122Z"},{"affected":"\u2264 3.5.1","affected_versions_present":true,"cve_id":"CVE-2026-7620","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-7620","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-07-13T14:39:54.504Z","patch_url":"","primary_source":"","published":"2026-07-11T03:44:20.239Z"},{"affected":"n/a \u2264 3.5","affected_versions_present":true,"cve_id":"CVE-2026-40732","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-40732","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-06-16T13:35:37.184Z","patch_url":"","primary_source":"","published":"2026-06-15T20:18:11.884Z"},{"affected":"Notification for Telegram: \u2264 3.5.1","affected_versions_present":true,"cve_id":"CVE-2025-62993","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-62993","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-04-28T16:14:08.089Z","patch_url":"","primary_source":"","published":"2025-12-09T14:52:25.243Z"},{"affected":"\u2264 3.5","affected_versions_present":true,"cve_id":"CVE-2025-58794","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-58794","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-05-12T00:46:36.044Z","patch_url":"","primary_source":"","published":"2025-09-05T13:45:03.746Z"},{"affected":"\u2264 3.3.1","affected_versions_present":true,"cve_id":"CVE-2024-9685","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-9685","fixed":"An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.","last_modified":"2026-04-08T17:14:41.711Z","patch_url":"https://plugins.trac.wordpress.org/changeset/3165615/notification-for-telegram","primary_source":"","published":"2024-10-10T02:06:10.487Z"}],"source_generated_at":"2026-10-08T06:18:52.353Z","vendor":"rainafarai"}}