CVE-2020-36719

ListingPro - WordPress Directory & Listing Theme < 2.6.1 - Arbitrary Plugin Installation, Activation and Deactivation

2020-12-17 00:00
Jerome Bruandet

Strategic Overview

Status
Patched in 2.6.1
Affected Version
< 2.6.1
CVSS
9.8Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2020-36719
View all ListingPro - WordPress Directory & Listing Theme vulnerabilities

At a glance

CVE-2020-36719 is a critical-severity Missing Authorization vulnerability in the ListingPro - WordPress Directory & Listing Theme WordPress theme, affecting versions < 2.6.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.6.1; sites on affected versions should update now. Disclosed December 2020, reported by Jerome Bruandet.

Vulnerability Overview

The ListingPro - WordPress Directory & Listing Theme for WordPress is vulnerable to Arbitrary Plugin Installation, Activation and Deactivation in versions before 2.6.1. This is due to a missing capability check on the lp_cc_addons_actions function. This makes it possible for unauthenticated attackers to arbitrarily install, activate and deactivate any 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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in ListingPro - WordPress Directory & Listing Theme < 2.6.1 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 ListingPro - WordPress Directory & Listing Theme the fix is 2.6.1: builds < 2.6.1 are affected, anything from 2.6.1 onward is not.

Remediation

Update to version 2.6.1, 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: ListingPro - WordPress Directory & Listing Theme 2.6.1 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