HomeWordPress vulnerabilitiesCubeWP Framework
CubeWP Framework vulnerabilities
CubeWP Framework has 8 known vulnerabilities in this database. The most recent published record is dated 10 Aug 2026.
- Known vulnerabilities
- 8
- Active installs
- 4,000+
- Latest version
- 1.1.31
- Last updated
- 29 Jul 2026
- Most recent
- 10 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-17018 | Medium 4.9 | Up to 1.1.30 | Fixed in a later version (latest 1.1.31) | 10 Aug 2026 |
| SQL injection CVE-2026-17017 | High 8.1 | Before 1.1.31 | Fixed in 1.1.31 | 9 Aug 2026 |
| Path traversal CVE-2026-13339 | High 7.5 | Up to 1.1.30 | Fixed in a later version (latest 1.1.31) | 2 Aug 2026 |
| SQL injection CVE-2026-6453 | Medium 6.5 | Up to 1.1.30 | Fixed in a later version (latest 1.1.31) | 1 Aug 2026 |
| Sensitive data exposure CVE-2025-6461 | Medium 4.3 | Up to 1.1.27 | Fixed in a later version (latest 1.1.31) | 25 Jan 2026 |
| Cross-site scripting (XSS) CVE-2025-8615 | Medium 6.4 | Up to 1.1.26 | Fixed in a later version (latest 1.1.31) | 17 Jan 2026 |
| Sensitive data exposure CVE-2025-12129 | Medium 5.3 | Up to 1.1.27 | Fixed in a later version (latest 1.1.31) | 17 Jan 2026 |
| Privilege escalation CVE-2025-4315 | High 8.8 | Before 1.1.24 | Fixed in 1.1.24 | 11 Jun 2025 |
Read the published descriptions
- CVE-2026-17018, 10 Aug 2026
- The CubeWP Framework WordPress plugin through 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 record
- CVE-2026-17017, 9 Aug 2026
- The CubeWP Framework WordPress plugin before 1.1.31 does not properly sanitize and escape a parameter before using it in a SQL statement through an AJAX action, and does not include a capability check on that action, allowing users with Subscriber-level access and above to perform SQL injection attacks. CVE record
- CVE-2026-13339, 2 Aug 2026
- 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. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. This is exploitable by unauthenticated attackers 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. CVE record
- CVE-2026-6453, 1 Aug 2026
- 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 record
- CVE-2025-6461, 25 Jan 2026
- The CubeWP - All-in-One Dynamic Content Framework plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.1.27 via the search feature in class-cubewp-search-ajax-hooks.php due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to. CVE record
- CVE-2025-8615, 17 Jan 2026
- The CubeWP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's cubewp_shortcode_taxonomy shortcode in all versions up to, and including, 1.1.26 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2025-12129, 17 Jan 2026
- The CubeWP - All-in-One Dynamic Content Framework plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.1.27 via the /cubewp-posts/v1/query-new and /cubewp-posts/v1/query REST API endpoints due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to. CVE record
- CVE-2025-4315, 11 Jun 2025
- The CubeWP - All-in-One Dynamic Content Framework plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.1.23. This is due to the plugin allowing a user to update arbitrary user meta through the update_user_meta() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges to that of an administrator. CVE record
What to do if you run CubeWP Framework
If you run CubeWP Framework, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new CubeWP Framework vulnerabilities
Free. We email you when a new vulnerability is published for CubeWP Framework, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.