CVE-2025-50017
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?
CVE-2025-50017 is a Cross Site Scripting (XSS) vulnerability in the WordPress WP Voting Contest plugin up to version 5.8. It allows a malicious user with at least Editor-level privileges to inject malicious scripts, such as redirects or advertisements, into the website. These scripts execute when visitors access the site, potentially compromising the site's integrity and user experience. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to inject malicious scripts that execute in visitors' browsers, potentially leading to unauthorized redirects, display of unwanted advertisements, or other harmful HTML payloads. This can harm your website's reputation, compromise user trust, and possibly lead to further exploitation or malware infection. Although the severity is considered low, attackers may attempt automated exploitation. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for malicious script injections in the WP Voting Contest plugin, especially from users with Editor-level privileges. Since plugin-based malware scanners can be unreliable, it is recommended to perform server-side malware scanning and seek professional incident response if compromise is suspected. Specific commands are not provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) provided by Patchstack, which auto-mitigates the vulnerability without an official fix and without impacting performance. Additionally, restricting Editor-level user privileges and monitoring for suspicious activity can help reduce risk. Since no official patch is available, these measures are currently the best options. [1]