CVE-2025-24771
BaseFortify
Publication date: 2025-07-04
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 reflected Cross Site Scripting (XSS) flaw in the WordPress Content Manager Light plugin up to version 3.2. It allows unauthenticated attackers to inject malicious scripts, such as redirects, advertisements, or other HTML payloads, into websites using the plugin. These scripts execute when visitors access the affected site, potentially compromising user interactions. [1]
How can this vulnerability impact me? :
The vulnerability can lead to attackers injecting malicious scripts that execute in the browsers of site visitors. This can result in unauthorized actions like redirecting users to malicious sites, displaying unwanted advertisements, stealing user data, or performing other harmful activities. Since the plugin is abandoned with no official fix, the risk remains unless mitigated by a virtual patch or plugin replacement. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be performed by monitoring for reflected XSS attack patterns targeting the Content Manager Light plugin, such as suspicious URL parameters containing script payloads. Since no official detection commands are provided, users can inspect HTTP requests for unusual script injections in URLs or use web application scanners that detect reflected XSS vulnerabilities. Additionally, applying the Patchstack virtual patch can help block attack attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the Patchstack virtual patch (vPatch) to block attacks exploiting this vulnerability until an official fix is released. Users are also advised to consider replacing the plugin entirely, as simply deactivating it does not remove the security risk. [1]