CVE-2026-84066

Directorist: AI-Powered Business Directory, Listings & Classified Ads < 8.9 - Authenticated (Subscriber+) Insecure Direct Object Reference

2026-09-04 00:00
Ryan Zegar

Strategic Overview

Status
Patched in 8.9
Affected Version
< 8.9
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-84066
View all Directorist: AI-Powered Business Directory, Listings & Classified Ads vulnerabilities

At a glance

CVE-2026-84066 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Directorist WordPress plugin, affecting versions < 8.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 8.9; sites on affected versions should update now. Disclosed September 2026, reported by Ryan Zegar.

Vulnerability Overview

The Directorist: AI-Powered Business Directory, Listings & Classified Ads plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to 8.9. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Directorist < 8.9 takes an account at Subscriber level or above. 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 Directorist the fix is 8.9: builds < 8.9 are affected, anything from 8.9 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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