CVE-2026-6453 CubeWP Framework <= 1.1.30 - Authenticated (Subscriber+) SQL Injection via 'relation_id' Parameter
Authenticated attackers with subscriber access can execute arbitrary SQL queries via the relation_id parameter in the CubeWP Framework plugin.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-6453?
CVE-2026-6453 is a medium-severity SQL injection vulnerability in cubewp1211 CubeWP Framework, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-89
Which versions are affected by CVE-2026-6453?
How do I fix CVE-2026-6453?
No fix has been published for CVE-2026-6453 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-6453 being exploited?
There is no known exploitation of CVE-2026-6453 in the wild and no public exploit code.
Sources
Also known as GHSA-fg67-hgjg-74qh.