Qi Blocks <= 1.4.3 - Missing Authorization to Authenticated (Contributor+) Plugin Settings Update
Strategic Overview
- Status
- Patched in 1.4.4
- Affected Plugin
- Qi Blocks
- Affected Version
<= 1.4.3- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-12180
At a glance
CVE-2025-12180 is a medium-severity Missing Authorization vulnerability in the Qi Blocks WordPress plugin, affecting versions <= 1.4.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.4.4; sites on affected versions should update now. Disclosed October 2025, reported by Adrian Lukita.
Vulnerability Overview
The Qi Blocks plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.4.3. This is due to the plugin storing arbitrary CSS styles submitted via the `qi-blocks/v1/update-styles` REST API endpoint without proper sanitization in the `update_global_styles_callback()` function. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary CSS, which can be used to perform actions such as hiding content, overlaying fake UI elements, or exfiltrating sensitive information via CSS injection techniques.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Qi Blocks <= 1.4.3 carries this weakness at update_global_styles_callback(), and reaching it takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Qi Blocks the fix is 1.4.4: builds <= 1.4.3 are affected, anything from 1.4.4 onward is not.
Remediation
Update to version 1.4.4, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Qi Blocks 1.4.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Qi Blocks
- 8.8CVE-2024-49690: Qi Blocks <= 1.3.2 Local File Inclusion
CVE-2024-49690 - 6.4CVE-2025-64383: Qi Blocks <= 1.4.3 Stored Cross-Site Scripting
CVE-2025-64383 - 6.4CVE-2024-38712: Qi Blocks <= 1.3 Stored Cross-Site Scripting
CVE-2024-38712 - 6.4CVE-2024-5221: Qi Blocks <= 1.2.9 Stored Cross-Site Scripting
CVE-2024-5221 - 5.4CVE-2025-1626: Qi Blocks <= 1.3.6 Stored Cross-Site Scripting
CVE-2025-1626 - 5.4CVE-2025-1625: Qi Blocks <= 1.3.6 Stored Cross-Site Scripting
CVE-2025-1625 - 5.4CVE-2025-1627: Qi Blocks <= 1.3.6 Stored Cross-Site Scripting
CVE-2025-1627 - 4.3CVE-2026-10096: Qi Blocks IDOR
CVE-2026-10096
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C