CVE-2025-4315

CubeWP – All-in-One Dynamic Content Framework <= 1.1.23 - Authenticated (Subscriber+) Privilege Escalation

2025-06-10 00:00
Foxyyy

Strategic Overview

Status
Patched in 1.1.24
Affected Plugin
CubeWP Framework
Affected Version
<= 1.1.23
CVSS
8.8High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2025-4315
View all CubeWP Framework vulnerabilities

At a glance

CVE-2025-4315 is a high-severity Improper Privilege Management vulnerability in the CubeWP Framework WordPress plugin, affecting versions <= 1.1.23. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.24; sites on affected versions should update now. Disclosed June 2025, reported by Foxyyy.

Vulnerability Overview

The CubeWP – All-in-One Dynamic Content Framework plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.1.23. This is due to the plugin allowing a user to update arbitrary user meta through the update_user_meta() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges to that of an administrator.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-269: Improper Privilege Management

CubeWP Framework <= 1.1.23 carries this weakness at update_user_meta(), and reaching it takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For CubeWP Framework the fix is 1.1.24: builds <= 1.1.23 are affected, anything from 1.1.24 onward is not.

Remediation

Update to version 1.1.24, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: CubeWP Framework 1.1.24 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-4315https://www.wordfence.com/threat-intel/vulnerabilities/id/430b7e72-72b8-4cf8-99f4-ee1d1d4b4f24https://nvd.nist.gov/vuln/detail/CVE-2025-4315

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C