CVE-2025-49882
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?
This vulnerability is a Cross-Site Scripting (XSS) issue in the CubeWP Framework WordPress plugin up to version 1.1.23. It allows attackers with contributor-level privileges to inject malicious scripts into web pages generated by the plugin. These scripts can execute in the browsers of visitors to the affected website, potentially causing redirects, displaying unwanted advertisements, or executing other harmful HTML payloads. The vulnerability is DOM-based and classified under OWASP Top 10 category A3: Injection. [1]
How can this vulnerability impact me? :
The impact of this vulnerability includes unauthorized execution of malicious scripts on your website, which can compromise website integrity and negatively affect user experience. Attackers could use it to redirect visitors, display unwanted content, or perform other malicious actions. Although the severity is considered low (CVSS 6.5), exploitation could still lead to security issues. It requires only contributor-level privileges to exploit, so users with such access could trigger the attack. Prompt updating to version 1.1.24 or later is recommended to mitigate the risk. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking the version of the CubeWP Framework plugin installed on your WordPress site. Versions up to and including 1.1.23 are vulnerable. You can detect the plugin version via WordPress admin dashboard or by running commands to check the plugin files. For example, using WP-CLI: `wp plugin list` to see installed plugin versions. Additionally, monitoring for suspicious script injections or unexpected redirects in web traffic logs may help identify exploitation attempts. However, plugin-based scanners may be unreliable; professional incident response and server-side malware scanning are recommended if compromise is suspected. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the CubeWP Framework plugin to version 1.1.24 or later, where the vulnerability is fixed. Enabling auto-updates for the plugin is also recommended to ensure timely patching. If updating immediately is not possible, applying virtual patching (vPatching) offered by Patchstack can help auto-mitigate the vulnerability. In case of suspected compromise, professional incident response and server-side malware scanning should be performed. [1]