CVE-2025-58794
BaseFortify
Publication date: 2025-09-05
Last updated on: 2026-04-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| patchstack | notification_for_telegram | * |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
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]
How can this vulnerability impact me? :
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]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
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]
What immediate steps should I take to mitigate this vulnerability?
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]