CVE-2025-57935
BaseFortify
Publication date: 2025-09-22
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 | bot_block_stop_spam_referrals_in_google_analytics | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) flaw in the WordPress plugin "Bot Block – Stop Spam Referrals in Google Analytics" versions up to 2.6. It allows an attacker with administrator privileges to inject malicious scripts into the website. These scripts can execute when visitors access the site, potentially causing redirects, displaying unwanted advertisements, or executing other harmful HTML payloads. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability can lead to unauthorized script execution on your website. This can result in malicious redirects, unwanted advertisements, or other harmful actions affecting your site visitors. Since the plugin is abandoned and unpatched, the risk remains unless the plugin is removed or a virtual patch is applied. The attacker needs administrator-level access to exploit this vulnerability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the WordPress plugin "Bot Block – Stop Spam Referrals in Google Analytics" version 2.6 or earlier is installed and active on your site. Since the vulnerability requires administrator-level access to exploit, monitoring for suspicious administrator activity or injected scripts in the website content may help detect exploitation attempts. There are no specific commands provided for detection in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include removing and replacing the vulnerable plugin rather than just deactivating it, as deactivation alone does not eliminate the risk. Applying a virtual patch (vPatch) from Patchstack can provide automatic protection in the absence of an official fix. Since the plugin appears abandoned with no official patch available, these steps are critical to reduce exposure. [1]