CVE-2023-0684

Wicked Folders <= 2.18.16 - Missing Authorization via ajax_unassign_folders

2023-02-06 00:00
Marco Wotschka

Strategic Overview

Status
Patched in 2.18.17
Affected Plugin
Wicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types
Affected Version
<= 2.18.16
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-0684
View all Wicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types vulnerabilities

At a glance

CVE-2023-0684 is a medium-severity Missing Authorization vulnerability in the Wicked Folders WordPress plugin, affecting versions <= 2.18.16. 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 2.18.17; sites on affected versions should update now. Disclosed February 2023, reported by Marco Wotschka.

Vulnerability Overview

The Wicked Folders plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the ajax_unassign_folders function in versions up to, and including, 2.18.16. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to invoke this function and perform actions intended for administrators such as changing the folder structure maintained by the plugin.

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 Wicked Folders <= 2.18.16 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 Wicked Folders the fix is 2.18.17: builds <= 2.18.16 are affected, anything from 2.18.17 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-0684https://www.wordfence.com/threat-intel/vulnerabilities/id/29358ea9-21b7-4294-8fc9-0d38e689cf53https://nvd.nist.gov/vuln/detail/CVE-2023-0684

Related records

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