CVE-2025-58794
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-05

Last updated on: 2026-04-28

Assigner: Patchstack

Description
Cross-Site Request Forgery (CSRF) vulnerability in rainafarai Notification for Telegram notification-for-telegram allows Cross Site Request Forgery.This issue affects Notification for Telegram: from n/a through <= 3.5.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-05
Last Modified
2026-04-28
Generated
2026-06-16
AI Q&A
2025-09-05
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
patchstack notification_for_telegram *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a Cross-Site Request Forgery (CSRF) issue in the WordPress Notification for Telegram Plugin up to version 3.4.6. It allows an attacker to trick authenticated users with higher privileges into performing unauthorized actions on the site without their consent, potentially compromising the site's integrity. Exploitation does not require authentication, making it easier for attackers to exploit. [1]

Impact Analysis

The vulnerability can impact you by allowing attackers to execute unauthorized actions on your site through tricking privileged users. This can compromise the integrity of your site, potentially leading to unauthorized changes or disruptions. Although the severity is rated low (CVSS 4.3), the risk is increased because no official patch is available and exploitation requires no authentication. [1]

Detection Guidance

Detection of this CSRF vulnerability in the Notification for Telegram plugin is challenging because exploitation requires no authentication and automated attacks may be opportunistic. Plugin-based malware scanners may be unreliable. There are no specific commands provided for detection. Users are advised to seek professional incident response services if compromise is suspected. [1]

Mitigation Strategies

Immediate mitigation steps include using Patchstack's virtual patching (vPatching) technology, which provides immediate protection even without an official fix. Since no official patch is available, applying virtual patches is recommended. Additionally, monitoring for suspicious activity and seeking professional incident response services if compromise is suspected are advised. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-58794. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart