Directorist: AI-Powered Business Directory, Listings & Classified Ads <= 8.10.2.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Listing Deletion via 'listing_id' Parameter
Strategic Overview
- Status
- Patched in 8.10.3
- Affected Version
<= 8.10.2.1- CVSS
- 8.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-17092
At a glance
CVE-2026-17092 is a high-severity Missing Authorization vulnerability in the Directorist WordPress plugin, affecting versions <= 8.10.2.1. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 8.10.3; sites on affected versions should update now. Disclosed October 2026, reported by Supakiad S. (m3ez).
Vulnerability Overview
The Directorist: AI-Powered Business Directory, Listings & Classified Ads plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 8.10.2.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary business directory listings, including those owned by other users and posts in publish, draft, or private status. The nonces guarding the endpoint do not constitute an authorization barrier because both directorist_nonce and atbdp_nonce_js are exposed to all logged-in users via wp_localize_script.
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, availability.
CWE-862: Missing Authorization
Reaching this weakness in Directorist <= 8.10.2.1 takes an account at Subscriber level or above. 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 Directorist the fix is 8.10.3: builds <= 8.10.2.1 are affected, anything from 8.10.3 onward is not.
Remediation
Update to version 8.10.3, 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.10.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 6.5CVE-2025-12174: Directorist Authenticated (Subscriber+) Data Export
CVE-2025-12174 - 6.3CVE-2022-2377: Directorist Missing Authorization
CVE-2022-2377 - 5.3CVE-2026-39509: Directorist <= 8.5.10 Missing Authorization
CVE-2026-39509 - 5.3CVE-2025-2224: Directorist Unauthenticated Arbitrary Post Publishing
CVE-2025-2224
Other vulnerabilities in Directorist: AI-Powered Business Directory, Listings & Classified Ads
- 8.8CVE-2023-1888: Directorist Arbitrary User Password Reset
CVE-2023-1888 - 8.8CVE-2022-3930: Directorist IDOR to Arbitrary User Password Change
CVE-2022-3930 - 8.8CVE-2021-24981: Directorist <= 7.0.6.1 CSRF to Arbitrary File Upload
CVE-2021-24981 - 8.1CVE-2025-10488: Directorist Arbitrary File Move
CVE-2025-10488 - 8.1CVE-2025-1570: Directorist Privilege Escalation and Account Takeover
CVE-2025-1570 - 7.5CVE-2026-59518: Directorist PHP Object Injection
CVE-2026-59518 - 7.5CVE-2022-2376: Directorist <= 7.3.0 Sensitive Information Disclosure
CVE-2022-2376 - 7.2CVE-2023-2252: Directorist <= 7.5.3 Local File Inclusion
CVE-2023-2252
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C