CVE-2021-4345

uListing <= 1.6.6 - Unauthenticated Arbitrary Roles and Capabilities Creation/Deletion

2021-01-28 00:00
Jerome Bruandet

Strategic Overview

Status
Patched in 1.7
Affected Plugin
Directory Listings WordPress plugin – uListing
Affected Version
< 1.7
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2021-4345
View all Directory Listings WordPress plugin – uListing vulnerabilities

At a glance

CVE-2021-4345 is a medium-severity Missing Authorization vulnerability in the Directory Listings WordPress plugin WordPress plugin, affecting versions < 1.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.7; sites on affected versions should update now. Disclosed January 2021, reported by Jerome Bruandet.

Vulnerability Overview

The uListing plugin for WordPress is vulnerable to authorization bypass due to missing capability and nonce checks on the UlistingUserRole::save_role_api method in versions up to, and including, 1.6.6. This makes it possible for unauthenticated attackers to remove or add roles, and add capabilities.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Directory Listings WordPress plugin < 1.7 takes no account at all. 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 Directory Listings WordPress plugin the fix is 1.7: builds < 1.7 are affected, anything from 1.7 onward is not.

Remediation

Update to version 1.7, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Directory Listings WordPress plugin 1.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-4345https://www.wordfence.com/threat-intel/vulnerabilities/id/44e112a7-8f51-4d2a-a4b3-74a47ef3aec7https://nvd.nist.gov/vuln/detail/CVE-2021-4345

Related records

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