CVE-2026-17018

CubeWP Framework <= 1.1.30 - Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary Post and User Meta Disclosure

2026-08-05 00:00
Muni Nitish Kumar Yaddala

Strategic Overview

Status
Unpatched
Affected Plugin
CubeWP Framework
Affected Version
<= 1.1.30
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-17018
View all CubeWP Framework vulnerabilities

At a glance

CVE-2026-17018 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the CubeWP Framework WordPress plugin, affecting versions <= 1.1.30. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by Muni Nitish Kumar Yaddala.

Vulnerability Overview

The CubeWP Framework plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 1.1.30. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorized action.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in CubeWP Framework <= 1.1.30 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. No fixed build of this plugin is recorded for CubeWP Framework yet, so installs running <= 1.1.30 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-17018https://www.wordfence.com/threat-intel/vulnerabilities/id/94f0aa43-3d36-4e02-8d96-5d0a2bd8dbd9https://nvd.nist.gov/vuln/detail/CVE-2026-17018

Related records

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