Qi Blocks at a glance
- 10 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Jun 30, 2026.
- Ranked #675 by popularity on WordPress.org (60,000+ active installs).
- The latest version is 1.5.4 (released Oct 22, 2026). The most recent security fix shipped in 1.5.0.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Qi Blocks version
Enter the Qi Blocks 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 “Qi Blocks”, 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.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Qi Blocks”.
- 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
Update
Click “Update now” to move to the latest version (1.5.4). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Qi Blocks vulnerabilities
Qi Blocks <= 1.4.9 - Insecure Direct Object Reference to Authenticated (Author+) Arbitrary Style Modification via 'page_id' Parameter
Missing authorization · CVE-2026-10096
Affected versions: ≤ 1.4.9
Fixed in: 1.5.0
Severity: Medium 4.3 · Disclosed Jun 30, 2026
Qi Blocks <= 1.4.3 - Missing Authorization to Arbitrary Attachment Resize
Missing authorization · CVE-2025-12182
Affected versions: ≤ 1.4.3
Fixed in: 1.4.4
Severity: Medium 4.3 · Disclosed Nov 14, 2025
Qi Blocks <= 1.4.3 - Missing Authorization to Authenticated (Contributor+) Plugin Settings Update
Missing authorization · CVE-2025-12180
Affected versions: ≤ 1.4.3
Fixed in: 1.4.4
Severity: Medium 4.3 · Disclosed Oct 31, 2025
Qi Blocks <= 1.4.3 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2025-64383
Affected versions: ≤ 1.4.3
Fixed in: 1.4.4
Severity: Medium 6.4 · Disclosed Aug 11, 2025
Qi Blocks <= 1.3.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via Countdown Block
Cross-site scripting (XSS) · CVE-2025-1626
Affected versions: ≤ 1.3.6
Fixed in: 1.4
Severity: Medium 5.4 · Disclosed Apr 28, 2025
Qi Blocks <= 1.3.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via Counter Block
Cross-site scripting (XSS) · CVE-2025-1625
Affected versions: ≤ 1.3.6
Fixed in: 1.4
Severity: Medium 5.4 · Disclosed Apr 28, 2025
Qi Blocks <= 1.3.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via ToC Block
Cross-site scripting (XSS) · CVE-2025-1627
Affected versions: ≤ 1.3.6
Fixed in: 1.4
Severity: Medium 5.4 · Disclosed Apr 28, 2025
Qi Blocks <= 1.3.2 - Authenticated (Contributor+) Local File Inclusion
Arbitrary file read or deletion · CVE-2024-49690
Affected versions: ≤ 1.3.2
Fixed in: 1.3.3
Severity: High 8.8 · Disclosed Oct 21, 2024
Qi Blocks <= 1.3 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-38712
Affected versions: ≤ 1.3
Fixed in: 1.3.1
Severity: Medium 6.4 · Disclosed Jul 11, 2024
Qi Blocks <= 1.2.9 - Authenticated (Author+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-5221
Affected versions: ≤ 1.2.9
Fixed in: 1.3.0
Severity: Medium 6.4 · Disclosed Jun 5, 2024
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Qi Blocks <= 1.4.9 - Insecure Direct Object Reference to Authenticated (Author+) Arbitrary Style Modification via 'page_id' ParameterMissing authorization · CVE-2026-10096 | ≤ 1.4.9 | 1.5.0 | Medium 4.3 | Jun 30, 2026 |
| Qi Blocks <= 1.4.3 - Missing Authorization to Arbitrary Attachment ResizeMissing authorization · CVE-2025-12182 | ≤ 1.4.3 | 1.4.4 | Medium 4.3 | Nov 14, 2025 |
| Qi Blocks <= 1.4.3 - Missing Authorization to Authenticated (Contributor+) Plugin Settings UpdateMissing authorization · CVE-2025-12180 | ≤ 1.4.3 | 1.4.4 | Medium 4.3 | Oct 31, 2025 |
| Qi Blocks <= 1.4.3 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2025-64383 | ≤ 1.4.3 | 1.4.4 | Medium 6.4 | Aug 11, 2025 |
| Qi Blocks <= 1.3.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via Countdown BlockCross-site scripting (XSS) · CVE-2025-1626 | ≤ 1.3.6 | 1.4 | Medium 5.4 | Apr 28, 2025 |
| Qi Blocks <= 1.3.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via Counter BlockCross-site scripting (XSS) · CVE-2025-1625 | ≤ 1.3.6 | 1.4 | Medium 5.4 | Apr 28, 2025 |
| Qi Blocks <= 1.3.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via ToC BlockCross-site scripting (XSS) · CVE-2025-1627 | ≤ 1.3.6 | 1.4 | Medium 5.4 | Apr 28, 2025 |
| Qi Blocks <= 1.3.2 - Authenticated (Contributor+) Local File InclusionArbitrary file read or deletion · CVE-2024-49690 | ≤ 1.3.2 | 1.3.3 | High 8.8 | Oct 21, 2024 |
| Qi Blocks <= 1.3 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-38712 | ≤ 1.3 | 1.3.1 | Medium 6.4 | Jul 11, 2024 |
| Qi Blocks <= 1.2.9 - Authenticated (Author+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-5221 | ≤ 1.2.9 | 1.3.0 | Medium 6.4 | Jun 5, 2024 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Jun 30, 2026.
Most common weaknesses in Qi Blocks
Cross-site scripting (XSS)
6 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.
Missing authorization
3 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.
Arbitrary file read or deletion
1 issue
An attacker can read or delete files on the server. Deleting a configuration file can take the site offline, and reading one can expose passwords.
Frequently asked questions
Is Qi Blocks safe to use?
Qi Blocks is a well-known plugin with 60,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.5.4) and turn on automatic updates.
How do I find which version of Qi Blocks 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.