HomeWordPress vulnerabilitiesQubely
Qubely vulnerabilities
Qubely has 5 known vulnerabilities in this database. The most recent published record is dated 11 Mar 2025.
- Known vulnerabilities
- 5
- Active installs
- 7,000+
- Latest version
- 1.8.14
- Last updated
- 10 Mar 2025
- Most recent
- 11 Mar 2025
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 |
|---|---|---|---|---|
| Sensitive data exposure CVE-2024-13228 | Medium 4.3 | Before 1.8.14 | Fixed in 1.8.14 | 11 Mar 2025 |
| Cross-site scripting (XSS) CVE-2024-9601 | Medium 6.5 | Before 1.8.13 | Fixed in 1.8.13 | 14 Feb 2025 |
| Cross-site scripting (XSS) CVE-2023-0376 | Medium 5.4 | Before 1.8.5 | Fixed in 1.8.5 | 16 Jan 2024 |
| Security weakness CVE-2021-24916 | High 7.5 | Before 1.8.6 | Fixed in 1.8.6 | 7 Aug 2023 |
| Cross-site request forgery (CSRF) CVE-2021-25013 | Medium 6.5 | Before 1.7.8 | Fixed in 1.7.8 | 24 Jan 2022 |
Read the published descriptions
- CVE-2024-13228, 11 Mar 2025
- The Qubely - Advanced Gutenberg Blocks plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.13 via the 'qubely_get_content'. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive private, pending, scheduled, password-protected, draft, and trashed post data. CVE record
- CVE-2024-9601, 14 Feb 2025
- The Qubely - Advanced Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘align’ and 'UniqueID' parameter in all versions up to, and including, 1.8.12 due to insufficient input sanitization and output escaping. 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-2025-26767 is a duplicate of this issue. CVE record
- CVE-2023-0376, 16 Jan 2024
- The Qubely WordPress plugin before 1.8.5 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks. CVE record
- CVE-2021-24916, 7 Aug 2023
- The Qubely WordPress plugin before 1.8.6 allows unauthenticated user to send arbitrary e-mails to arbitrary addresses via the qubely_send_form_data AJAX action. CVE record
- CVE-2021-25013, 24 Jan 2022
- The Qubely WordPress plugin before 1.7.8 does not have authorisation and CSRF check on the qubely_delete_saved_block AJAX action, and does not ensure that the block to be deleted belong to the plugin, as a result, any authenticated users, such as subscriber can delete arbitrary posts CVE record
What to do if you run Qubely
If you run Qubely, 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 Qubely vulnerabilities
Free. We email you when a new vulnerability is published for Qubely, 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.