CVE-2025-50026
BaseFortify
Publication date: 2025-06-20
Last updated on: 2026-04-28
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 Spoki plugin up to version 2.16.0. 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 the site's integrity and user experience. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability can allow an attacker to execute malicious scripts on your website, which can lead to unauthorized redirects, display of unwanted advertisements, or other harmful HTML content. This can damage your website's reputation, compromise user trust, and potentially lead to further security issues. However, the vulnerability 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 Spoki plugin, especially those inserted by users with administrator privileges. Since the vulnerability allows stored XSS payloads, inspecting the website content for unexpected redirects, advertisements, or HTML payloads can help. There are no specific commands provided for detection. Users are advised to perform 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 automatically protects sites from this vulnerability even without an official fix. Users should monitor for updates from the plugin developers, consider virtual patching as a temporary measure, and if a compromise is suspected, seek professional incident response and server-side malware scanning. Since no official patch is available, relying solely on plugin-based malware scanners is not recommended. [1]