CVE-2023-23882

Ultimate Addons for Beaver Builder - Lite <= 1.5.5 - Authenticated (Subscriber+) Settings Change

2023-01-24 00:00
István Márton

Strategic Overview

Status
Patched in 1.5.6
Affected Version
<= 1.5.5
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-23882
View all Ultimate Addons for Beaver Builder – Lite vulnerabilities

At a glance

CVE-2023-23882 is a medium-severity Missing Authorization vulnerability in the Ultimate Addons for Beaver Builder WordPress plugin, affecting versions <= 1.5.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.5.6; sites on affected versions should update now. Disclosed January 2023, reported by István Márton.

Vulnerability Overview

The Ultimate Addons for Beaver Builder - Lite plugin for WordPress is vulnerable to authorization bypass due to a missing capability and nonce check on the 'fetch_cloud_templates' function in versions up to, and including, 1.5.5. This makes it possible for subscriber-level attackers to refresh the plugin's cloud templates.

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

Ultimate Addons for Beaver Builder <= 1.5.5 carries this weakness at fetch_cloud_templates, and reaching it takes an account at Subscriber 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 Ultimate Addons for Beaver Builder the fix is 1.5.6: builds <= 1.5.5 are affected, anything from 1.5.6 onward is not.

Remediation

Update to version 1.5.6, 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: Ultimate Addons for Beaver Builder 1.5.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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