CVE-2022-45353

Betheme <= 26.6.2 - Missing Authorization Checks to Private Page/Post Data Disclosure

2022-11-21 00:00
Dave Jong

Strategic Overview

Status
Patched in 26.6.3
Affected Theme
Betheme
Affected Version
<= 26.6.2
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-45353
View all Betheme vulnerabilities

At a glance

CVE-2022-45353 is a medium-severity Missing Authorization vulnerability in the Betheme WordPress theme, affecting versions <= 26.6.2. It carries a CVSS score of 4.3 (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 26.6.3; sites on affected versions should update now. Disclosed November 2022, reported by Dave Jong.

Vulnerability Overview

The Betheme theme for WordPress is vulnerable to authorization bypass in versions up to, and including, 26.6.2. This is due to a missing capability check on the mfnvb_init_vb() function that initializes the visual editor for the plugin and discloses the plugin's page builder nonces and functionality to an attacker. This makes it possible for authenticated attacks with minimal permissions, such as a subscriber, to trigger the Betheme page editor for any post or page and view the information along with make any changes to the post/page accessed through the editor. This CVE is specific to viewing private page data that should otherwise be restricted. This is an extension of CVE-2022-45356.

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

Betheme <= 26.6.2 carries this weakness at mfnvb_init_vb(), 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 Betheme the fix is 26.6.3: builds <= 26.6.2 are affected, anything from 26.6.3 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-45353https://www.wordfence.com/threat-intel/vulnerabilities/id/f8068fb3-5a19-4b17-848b-32cebfff2537https://nvd.nist.gov/vuln/detail/CVE-2022-45353

Related records

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