WordPress plugin · Updated daily · Source: Wordfence Intelligence

Qubely vulnerabilities: affected versions and fixes

Qubely has 7,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Qubely at a glance

  • 12 publicly disclosed vulnerabilities. The most recent was disclosed on Jul 23, 2026.
  • Ranked #2592 by popularity on WordPress.org (7,000+ active installs).
  • The latest version is 1.8.14 (released Mar 10, 2025). The most recent security fix shipped in 1.8.14.
  • 4 vulnerabilities have no fix yet. Check the list below to see whether it affects how you use the plugin.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Qubely version

Enter the Qubely version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Qubely”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Qubely”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (1.8.14). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Qubely vulnerabilities

  • Qubely – Advanced Gutenberg Blocks <= 1.8.14 - Missing Authorization

    Missing authorization · CVE-2026-65531

    Affected versions: ≤ 1.8.14

    Fixed in: No fix yet

    Severity: Medium 5.3 · Disclosed Jul 23, 2026

  • Qubely <= 1.8.14 - Authenticated (Author+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-39638

    Affected versions: ≤ 1.8.14

    Fixed in: No fix yet

    Severity: Medium 6.4 · Disclosed Feb 14, 2026

  • Qubely <= 1.8.14 - Missing Authorization

    Missing authorization · CVE-2025-58663

    Affected versions: ≤ 1.8.14

    Fixed in: No fix yet

    Severity: Medium 5.4 · Disclosed Sep 22, 2025

  • Qubely <= 1.8.14 - Authenticated (Contributor+) Sensitive Information Exposure

    Information disclosure · CVE-2025-58249

    Affected versions: ≤ 1.8.14

    Fixed in: No fix yet

    Severity: Medium 4.3 · Disclosed Sep 22, 2025

  • Qubely – Advanced Gutenberg Blocks <= 1.8.13 - Authenticated (Contributor+) Sensitive Information Exposure via qubely_get_content

    Information disclosure · CVE-2024-13228

    Affected versions: ≤ 1.8.13

    Fixed in: 1.8.14

    Severity: Medium 4.3 · Disclosed Mar 10, 2025

  • Qubely <= 1.8.12 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-26767

    Affected versions: ≤ 1.8.12

    Fixed in: 1.8.13

    Severity: Medium 6.4 · Disclosed Feb 14, 2025

  • Qubely – Advanced Gutenberg Blocks <= 1.8.12 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'align' and 'UniqueID'

    Cross-site scripting (XSS) · CVE-2024-9601

    Affected versions: ≤ 1.8.12

    Fixed in: 1.8.13

    Severity: Medium 6.5 · Disclosed Feb 13, 2025

  • Qubely – Advanced Gutenberg Blocks <= 1.8.5 - Insufficient Authorization

    Other weakness · CVE-2021-24916

    Affected versions: < 1.8.6

    Fixed in: 1.8.6

    Severity: Medium 5.3 · Disclosed Jul 17, 2023

  • Quebely <= 1.8.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'className' Block Option

    Cross-site scripting (XSS) · CVE-2023-0376

    Affected versions: ≤ 1.8.4

    Fixed in: 1.8.5

    Severity: Medium 6.4 · Disclosed Feb 6, 2023

  • Qubely <= 1.7.9 - Incorrect Authorization

    Other weakness

    Affected versions: ≥ 1.8.0, ≤ 1.8.0

    Fixed in: 1.8.1

    Severity: Medium 5.4 · Disclosed Jun 14, 2022

  • Qubely <= 1.7.8 - Missing Authorization

    Missing authorization

    Affected versions: ≤ 1.7.8

    Fixed in: 1.7.9

    Severity: Medium 5.4 · Disclosed Jun 6, 2022

  • Qubely <= 1.7.7 - Missing Authorization to Arbitrary Post Deletion

    Missing authorization · CVE-2021-25013

    Affected versions: < 1.7.8

    Fixed in: 1.7.8

    Severity: Medium 5.4 · Disclosed Dec 27, 2021

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Jul 23, 2026.

Most common weaknesses in Qubely

Missing authorization

4 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Cross-site scripting (XSS)

4 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Information disclosure

2 issues

Data that should stay private, such as user details or configuration values, can be read from outside.

Frequently asked questions

Is Qubely safe to use?

Qubely is a well-known plugin with 7,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (1.8.14) and turn on automatic updates. That said, 4 issues have no fix yet, so check the list below.

How do I find which version of Qubely my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesQubely on WordPress.org