Qi Blocks <= 1.4.9 - Insecure Direct Object Reference to Authenticated (Author+) Arbitrary Style Modification via 'page_id' Parameter
Strategic Overview
- Status
- Patched in 1.5.0
- Affected Plugin
- Qi Blocks
- Affected Version
<= 1.4.9- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-10096
At a glance
CVE-2026-10096 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Qi Blocks WordPress plugin, affecting versions <= 1.4.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 1.5.0; sites on affected versions should update now. Disclosed June 2026, reported by Dmitrii Ignatyev.
Vulnerability Overview
The Qi Blocks plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.4.9 via the 'page_id' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with author-level access and above, to modify the stored Qi Blocks styles of arbitrary posts, templates, or widgets they do not own — including site-wide surfaces via the reserved 'template' and 'widget' page_id values — enabling unauthorized frontend defacement, content hiding, and degradation of any page on the site. The endpoint's permission_callback checks only the generic edit_posts and publish_posts capabilities, meaning any user with the built-in Author role satisfies the check regardless of post ownership.
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-639: Authorization Bypass Through User-Controlled Key
Qi Blocks <= 1.4.9 carries this weakness at page_id, and reaching it takes an account at Author level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Qi Blocks the fix is 1.5.0: builds <= 1.4.9 are affected, anything from 1.5.0 onward is not.
Remediation
Update to version 1.5.0, 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.5.0 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-2025-12182: Qi Blocks <= 1.4.3 Arbitrary Attachment Resize
CVE-2025-12182
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C