CVE-2025-50036
BaseFortify
Publication date: 2025-06-20
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
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) in the WordPress Mailing Group Listserv plugin up to version 3.0.5. It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions without their consent, potentially compromising site security. The vulnerability does not require authentication to exploit and is related to broken access control. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized actions being executed by privileged users on your site, which may compromise the security and integrity of your system. Although the severity is considered low (CVSS score 6.5) and exploitation is unlikely, successful attacks could disrupt availability or functionality. There is currently no official patch, so mitigation through virtual patching or monitoring is recommended. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this CSRF vulnerability in the WordPress Mailing Group Listserv plugin is challenging because plugin-based malware scanners may be unreliable. There are no specific commands provided for detection. Users should monitor for unusual actions performed by higher privileged users that could indicate exploitation. Virtual patching solutions can help neutralize the vulnerability proactively. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) to automatically neutralize the vulnerability without affecting performance, as no official patch or fixed version is currently available. Users should monitor for updates from the plugin vendor and consider professional incident response if compromise is suspected. [1]