CVE-2023-39998

Betheme <= 27.1.1 - Missing Authorization via '_tool_history_delete'

2023-08-10 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 27.1.2
Affected Theme
Betheme
Affected Version
<= 27.1.1
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-39998
View all Betheme vulnerabilities

At a glance

CVE-2023-39998 is a medium-severity Missing Authorization vulnerability in the Betheme WordPress theme, affecting versions <= 27.1.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high availability impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 27.1.2; sites on affected versions should update now. Disclosed August 2023, reported by Rafie Muhammad.

Vulnerability Overview

The Betheme theme for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the '_tool_history_delete' AJAX function in versions up to, and including, 27.1.1. This makes it possible for authenticated attackers, with author-level access and above, to delete site design revisions and backups.

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. A successful exploit has high impact on availability.

CWE-862: Missing Authorization

Betheme <= 27.1.1 carries this weakness at _tool_history_delete, 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 27.1.2: builds <= 27.1.1 are affected, anything from 27.1.2 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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