CVE-2023-31234

Tilda Publishing <= 0.3.23 - Missing Authorization

2023-09-04 00:00
spacecroupier

Strategic Overview

Status
Patched in 0.3.24
Affected Plugin
Tilda-publishing
Affected Version
<= 0.3.23
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-31234
View all Tilda-publishing vulnerabilities

At a glance

CVE-2023-31234 is a medium-severity Missing Authorization vulnerability in the Tilda-publishing WordPress plugin, affecting versions <= 0.3.23. 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 0.3.24; sites on affected versions should update now. Disclosed September 2023, reported by spacecroupier.

Vulnerability Overview

The Tilda Publishing plugin for WordPress is vulnerable to unauthorized access, modification, and loss of data due to missing capability checks on several functions hooked via AJAX actions such as 'ajax_export_file,' 'ajax_sync,' 'ajax_get_keys,' 'ajax_switcher_status,' and more in versions up to, and including, 0.3.23. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform a wide variety of actions like exporting data, modifying keys, and more.

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

Reaching this weakness in Tilda-publishing <= 0.3.23 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 Tilda-publishing the fix is 0.3.24: builds <= 0.3.23 are affected, anything from 0.3.24 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

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