CVE-2025-49316
BaseFortify
Publication date: 2025-06-17
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-49316 is a reflected Cross Site Scripting (XSS) vulnerability in the WordPress WP2LEADS plugin up to version 3.5.0. It allows unauthenticated attackers to inject malicious scripts, such as redirects, advertisements, or other HTML payloads, into web pages generated by the plugin. These scripts execute when visitors access the compromised site, potentially leading to security risks. The vulnerability is caused by improper neutralization of input during web page generation. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious scripts in the browsers of your website visitors. This can lead to unauthorized redirects, display of unwanted advertisements, theft of user data, session hijacking, or other malicious activities. It can compromise the security and trustworthiness of your website and potentially harm your users. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this reflected XSS vulnerability can be approached by monitoring for unusual script injections or redirects in web traffic involving the WP2LEADS plugin. Since the vulnerability allows injection of malicious scripts via web requests, inspecting HTTP request parameters for suspicious payloads may help. However, no specific commands are provided in the available resources. It is recommended to use professional incident response and server-side malware scanning tools rather than relying solely on plugin-based scanners to detect compromise. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the WP2LEADS plugin to version 3.5.1 or later, which contains the fix for this vulnerability. Until the update can be applied, applying the Patchstack virtual patch (vPatch) is advised, as it automatically blocks attacks exploiting this issue. Additionally, enabling auto-update options for the plugin can help ensure timely patching. Prompt patching is critical to prevent opportunistic automated attacks. [1]