WordPress security changelog
MEDIUM CVE-2026-6453 Received

CubeWP Subscribers can inject SQL through relation_id

CubeWP Framework through 1.1.30 passes the cubewp_remove_relation AJAX relation_id through wp_unslash() and sanitize_text_field(), then interpolates it into raw SQL without $wpdb->prepare(). A Subscriber-or-higher user can append SQL to the existing query; the record does not disclose the resulting data set or exact extraction method.

CVE / CNA score 6.5 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
CubeWP Framework
Plugin slug
cubewp-framework
Affected
<= 1.1.30
Safe version
> 1.1.30
Published
Aug 01, 2026
Weakness
CWE-89 — Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

This CVE was published Aug 01, 2026 and is one of 10 known issues for this plugin.

What to do

Update, patch or deactivate.

Update to a corrected release after 1.1.30. Review authenticated AJAX and database logs for crafted relation_id values, rotate disclosed credentials, and investigate database integrity where exploitation is suspected.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

References

Primary and upstream sources