CVE-2021-24318

Listeo - Directory & Listings With Booking - WordPress Theme < 1.6.11 - Insecure Direct Object Reference

2021-05-16 00:00
R3N0

Strategic Overview

Status
Patched in 1.6.11
Affected Version
< 1.6.11
CVSS
6.5Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2021-24318
View all Listeo - Directory & Listings With Booking - WordPress Theme vulnerabilities

At a glance

CVE-2021-24318 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Listeo - Directory & Listings With Booking - WordPress Theme WordPress theme, affecting versions < 1.6.11. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). The issue is fixed in version 1.6.11; sites on affected versions should update now. Disclosed May 2021, reported by R3N0.

Vulnerability Overview

The Listeo WordPress theme before 1.6.11 did not ensure that the Post/Page and Booking to delete belong to the user making the request, allowing any authenticated users to delete arbitrary page/post and booking via an IDOR vector.

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 integrity.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Listeo - Directory & Listings With Booking - WordPress Theme < 1.6.11 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Listeo - Directory & Listings With Booking - WordPress Theme the fix is 1.6.11: builds < 1.6.11 are affected, anything from 1.6.11 onward is not.

Remediation

Update to version 1.6.11, 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: Listeo - Directory & Listings With Booking - WordPress Theme 1.6.11 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