CVE-2026-6453

CubeWP Framework <= 1.1.30 - Authenticated (Subscriber+) SQL Injection via 'relation_id' Parameter

2026-07-31 20:01
Louis Deschanel (JeanJeanLeHaxor)

Strategic Overview

Status
Patched in 1.1.31
Affected Plugin
CubeWP Framework
Affected Version
<= 1.1.30
CVSS
6.5Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2026-6453
View all CubeWP Framework vulnerabilities

At a glance

CVE-2026-6453 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the CubeWP Framework WordPress plugin, affecting versions <= 1.1.30. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.31; sites on affected versions should update now. Disclosed July 2026, reported by Louis Deschanel (JeanJeanLeHaxor).

Vulnerability Overview

The CubeWP Framework plugin for WordPress is vulnerable to SQL Injection in all versions up to and including 1.1.30. This is due to insufficient input sanitization in the cubewp_remove_relation() AJAX function, specifically the use of wp_unslash() on the relation_id parameter before interpolating it directly into a raw SQL query without using $wpdb->prepare(). The wp_unslash() call explicitly removes the backslash escaping that WordPress's wp_magic_quotes() adds to all $_POST data, neutralizing the only layer of SQL injection protection. The sanitize_text_field() function applied afterward offers no SQL protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries to the existing query.

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.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CubeWP Framework <= 1.1.30 carries this weakness at cubewp_remove_relation(), and reaching it takes an account at Subscriber level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For CubeWP Framework the fix is 1.1.31: builds <= 1.1.30 are affected, anything from 1.1.31 onward is not.

Remediation

Update to version 1.1.31, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CubeWP Framework 1.1.31 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-6453https://www.wordfence.com/threat-intel/vulnerabilities/id/a4647620-e06a-49d5-8f9d-a59cb5a999b1https://nvd.nist.gov/vuln/detail/CVE-2026-6453

Related records

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