CVE-2025-50021
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-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) issue in the WordPress Better Random Redirect plugin up to version 1.3.20. It allows an attacker with administrator privileges to inject malicious scripts, such as redirects, advertisements, or other HTML payloads, into the website. These scripts execute when visitors access the site, potentially compromising user interactions. [1]
How can this vulnerability impact me? :
The vulnerability can allow attackers with admin access to inject malicious scripts that execute in visitors' browsers. This can lead to unwanted redirects, display of malicious advertisements, or other harmful actions affecting website visitors. It may damage user trust, lead to data theft, or facilitate further attacks. However, the risk is considered low severity and unlikely to be widely exploited. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for injected malicious scripts in the Better Random Redirect plugin, especially those inserted by users with administrator privileges. Since the vulnerability allows stored XSS payloads, inspecting the plugin's stored data for suspicious scripts is recommended. However, no specific detection commands are provided. It is advised to use server-side malware scanning and professional incident response if compromise is suspected. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) offered by Patchstack, which auto-mitigates the vulnerability without an official fix and without impacting performance. Users should maintain security vigilance, monitor for suspicious activity, and consider professional incident response or server-side malware scanning if compromise is suspected. Since no official patch is available, relying on vPatching and security best practices is recommended. [1]