Reported vulnerability

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

Published 31 Jul 2026

Updated 1 Aug 2026

CVE-2026-6453

Compare your installed software with the affected versions below. Follow the source’s remediation guidance and test an available update after taking a backup. A database entry describes a reported issue; it does not establish whether a particular website has been compromised.

Does this affect my version?

Check your installed version against this advisory. This compares the report’s version ranges and does not scan your website.

Wordfence advisory

medium · CVSS 6.5

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.

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

CubeWP Framework

Software: plugin · cubewp-framework
Affected versions: Start version unspecified, through 1.1.30
Fix availability: Fix available
Fixed versions: 1.1.31

Recommended action

Update to version 1.1.31, or a newer patched version

Further references (1)

wordfence.com/threat-intel/vulnerabilities/id/a4647620-e06a-49d5-8f9d-a59cb5a999b1?source=api-prod

Data sources and licences

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Read licence terms

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Read licence terms

Source: Wordfence

Need help fixing this issue?

Get help checking your site, applying an available update and resolving any problems after updating.

Get help with this issue

Questions about this vulnerability

Which versions of CubeWP Framework are affected?

Wordfence lists these affected versions: Start version unspecified, through 1.1.30. Use the version checker above to compare your installed release with this report.

Is a fix available for CubeWP Framework?

Wordfence reports a fix for this issue in CubeWP Framework. It lists these fixed versions: 1.1.31. Back up your website and test the recommended update before applying it to your live site.

Where can I find my installed plugin version?

In WordPress, open Plugins > Installed Plugins and find the version shown beneath the plugin name.

Does an affected version mean my website has been hacked?

An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.

These reports cover at least one of the same plugins, themes or WordPress core. Check each report’s affected versions separately.

Back to vulnerability database