CVE-2024-48039

CubeWP – All-in-One Dynamic Content Framework <= 1.1.15 - Missing Authorization

2024-10-09 00:00
Abdi Pranata

Strategic Overview

Status
Patched in 1.1.16
Affected Plugin
CubeWP Framework
Affected Version
<= 1.1.15
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-48039
View all CubeWP Framework vulnerabilities

At a glance

CVE-2024-48039 is a medium-severity Missing Authorization vulnerability in the CubeWP Framework WordPress plugin, affecting versions <= 1.1.15. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.1.16; sites on affected versions should update now. Disclosed October 2024, reported by Abdi Pranata.

Vulnerability Overview

The CubeWP – All-in-One Dynamic Content Framework plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on several funcstions like 'cwp_user_fields_data_callback ' and 'cwpform_save_shortcode' in versions up to, and including, 1.1.15. This makes it possible for authenticated attackers, with subscriber-level access and above, to update various plugin settings and export data.

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.

CWE-862: Missing Authorization

CubeWP Framework <= 1.1.15 carries this weakness at cwp_user_fields_data_callback, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For CubeWP Framework the fix is 1.1.16: builds <= 1.1.15 are affected, anything from 1.1.16 onward is not.

Remediation

Update to version 1.1.16, 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.16 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-48039https://www.wordfence.com/threat-intel/vulnerabilities/id/307e3e47-fac8-400d-9b90-b75b39ee14c3https://nvd.nist.gov/vuln/detail/CVE-2024-48039

Related records

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