CVE-2025-4315
BaseFortify
Publication date: 2025-06-11
Last updated on: 2025-07-10
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cubewp | cubewp | to 1.1.24 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo | |
| CWE-269 | The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the CubeWP WordPress plugin (up to version 1.1.23) allows authenticated users with Subscriber-level access or higher to escalate their privileges to administrator. This happens because the plugin's update_user_meta() function permits updating arbitrary user meta data without proper restrictions, enabling attackers to modify sensitive user metadata and gain elevated permissions. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with low-level access (Subscriber or above) to gain administrator privileges on the WordPress site. This can lead to full control over the site, including modifying content, installing malicious plugins, stealing data, or disrupting site operations. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
To detect this vulnerability, you can check if your WordPress site is running the CubeWP plugin version 1.1.23 or earlier, as these versions are vulnerable. Specifically, you can verify the plugin version via the WordPress admin dashboard or by checking the plugin files. Additionally, monitoring REST API calls that attempt to update user meta data could indicate exploitation attempts. Since the vulnerability involves unauthorized updates to user meta via the REST API, you can look for suspicious POST requests to the CubeWP REST API endpoints that include user meta updates. For example, using command-line tools like curl or network monitoring tools to inspect REST API traffic for calls to endpoints related to user meta updates. However, no specific detection commands are provided in the resources. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the CubeWP plugin to version 1.1.24 or later, which includes security enhancements that restrict REST API user meta updates to authorized fields only, preventing privilege escalation. This update hardens REST API endpoints by filtering input data against a whitelist of allowed fields based on user roles, effectively mitigating the vulnerability. Until the update is applied, restrict access to the REST API endpoints or limit user roles that can access the plugin's REST API to trusted users only. [1]