CVE-2026-6453
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk20th percentile - higher than 20% of all known CVEs
Summary
The CubeWP Framework plugin for WordPress is vulnerable to SQL injection in the `cubewp_remove_relation()` AJAX function. The use of `wp_unslash()` removes injection protection, and the lack of `$wpdb->prepare()` allows authenticated attackers with subscriber-level access to append additional SQL queries.
Risk Assessment
An attacker can read or modify database data, potentially leading to data leakage or site takeover.
Recommendation
Update the CubeWP Framework plugin to a version that uses prepared statements and proper sanitization.
Other vulnerabilities in CubeWP Framework
See all- CVE-2026-17018Medium
The CubeWP Framework WordPress plugin through version 1.1.30 does not perform a per-object read authorization check, nor restrict which metadata keys may be requested, on one of its REST API endpoints, allowing users with the Contributor role and above to read arbitrary post metadata (including that of other users' draft, pending, private, and password-protected posts) and arbitrary user metadata of any user, including administrators.
- CVE-2026-13339High
The CubeWP Framework plugin for WordPress is vulnerable to Directory Traversal in all versions up to and including 1.1.30 via the 'cubewp_get_svg_content' function. Unauthenticated attackers can read the contents of arbitrary files on the server, which can contain sensitive information. This is exploitable because the required nonce is publicly emitted into the markup of any page rendering the CubeWP posts shortcode or widget with AJAX loading enabled, making it harvestable by any guest visitor before submitting the AJAX request.
Original NVD description (English source)
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.