Qubely <= 1.7.8 - Missing Authorization

2022-06-06 00:00
Jan w Oleju

Strategic Overview

Status
Patched in 1.7.9
Affected Plugin
Qubely – Advanced Gutenberg Blocks
Affected Version
<= 1.7.8
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Qubely – Advanced Gutenberg Blocks vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the Qubely WordPress plugin, affecting versions <= 1.7.8. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.7.9; sites on affected versions should update now. Disclosed June 2022, reported by Jan w Oleju.

Vulnerability Overview

The Qubely plugin for WordPress contains a missing authorization weakness that makes it possible for subscriber-level users to update the plugin's settings in versions up to, and including 1.7.8. This is due to missing capability checks on the ajax_update_qubely_options() function called via the wp_ajax_update_qubely_options AJAX action that makes it callable via any authenticated user.

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

Qubely <= 1.7.8 carries this weakness at ajax_update_qubely_options(), and reaching it takes a caller who can reach the endpoint. 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 Qubely the fix is 1.7.9: builds <= 1.7.8 are affected, anything from 1.7.9 onward is not.

Remediation

Update to version 1.7.9, 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: Qubely 1.7.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/7681a661-21bd-42fb-ac97-1da808435520

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C