CVE-2025-8615
BaseFortify
Publication date: 2026-01-17
Last updated on: 2026-01-17
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cubewp | cubewp_framework | to 1.1.26 (inc) |
| cubewp | cubewp_framework | From 1.1.27 (inc) to 1.1.29 (inc) |
| cubewp | cubewp_plugin | to 1.1.26 (inc) |
| cubewp | cubewp_plugin | From 1.1.27 (inc) to 1.1.29 (inc) |
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-8615 is a Stored Cross-Site Scripting (XSS) vulnerability in the CubeWP plugin for WordPress. It occurs via the plugin's cubewp_shortcode_taxonomy shortcode in versions up to and including 1.1.26. The vulnerability is due to insufficient input sanitization and output escaping on user-supplied attributes, allowing authenticated attackers with contributor-level access or higher to inject arbitrary web scripts. These scripts execute whenever a user accesses the injected page, potentially compromising site security. [2]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with contributor-level access or higher to inject malicious scripts into pages on a WordPress site using the CubeWP plugin. When other users visit these pages, the injected scripts execute in their browsers, potentially leading to theft of user credentials, session hijacking, defacement, or other malicious actions. This can compromise the security and integrity of the website and its users. [2]
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability CVE-2025-8615 in the CubeWP WordPress plugin, you should update the plugin to version 1.1.27 or later, as these versions include security enhancements such as strengthened input sanitization and output escaping, improved nonce and capability checks, and other fixes to prevent stored cross-site scripting attacks. Additionally, ensure that only trusted users have contributor-level access or higher, as the vulnerability requires authenticated access at that level. [2]