CubeWP Framework vulnerabilities

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.

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.

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.