Skip to main content

Directorist CVE-2026-84098

| EUVDEUVD-2026-85035 MEDIUM
Incorrect Authorization (CWE-863)
2026-09-23 contact@wpscan.com GHSA-7mc4-vjfr-47h6
6.5
CVSS 3.1 · Vendor: wpscan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register free Subscriber account
  2. Delivery
    Enumerate target listing IDs
  3. Exploit
    Call unprotected listing-deletion endpoint
  4. Execution
    Bypass missing ownership check
  5. Impact
    Delete other users' arbitrary listings

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated account of at least Subscriber level on a WordPress site running the Directorist plugin from version 3.1.0 up to (but not including) 8.9.5 - practically exploitable wherever the site permits public self-registration (the default WordPress 'Anyone can register' setting), which is common on directory and classified-ad sites. Exploitation targets a specific unaddressed listing-deletion code path that the fixes for CVE-2023-1889 / CVE-2023-35052 did not cover; no elevated privileges, no user interaction, and no non-default plugin configuration are required beyond having the plugin installed. Limiting factor: sites that disable open registration or restrict Subscriber creation raise the bar to obtaining any valid account first.

Impact

This is a genuine but moderate-priority integrity issue. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, base 6.5) shows a network-reachable, low-complexity flaw requiring only Subscriber-level authentication (PR:L) and no user interaction - a low bar on any Directorist site that allows public registration, which many directory/classified sites do by design. The impact is integrity-only (I:H): destructive deletion of arbitrary listings, including those owned by other users. There is no confidentiality (C:N) or availability-of-service (A:N) impact, though loss of listings is effectively a data-destruction event for affected owners. Signal alignment: no EPSS score, no CISA KEV entry, and no public POC were provided, so this is not confirmed as actively exploited or trivially weaponized in the wild. However, one signal materially raises concern beyond the raw score: the description states this is an INCOMPLETE FIX of the previously-known CVE-2023-1889 / CVE-2023-35052, meaning the arbitrary-listing-deletion technique is already public knowledge from 2023 and attackers/researchers already understand the abuse path - only a new, unaddressed code path is being exploited. That prior-art history makes rediscovery and exploitation more plausible than the empty EPSS/KEV/POC fields alone would suggest. Net: real priority for any Directorist site with open registration, but not an emergency-patch/CISA-KEV-tier issue.

Exploit ScenarioDerived

An attacker registers a free Subscriber account on any WordPress site running Directorist before 8.9.5 (open self-registration is common on directory/classifieds sites). They then invoke the unprotected listing-deletion path - the one the 2023 fixes missed - supplying the ID of a listing they do not own, and the plugin deletes it without verifying ownership. Because this reuses a publicly documented technique from CVE-2023-1889/CVE-2023-35052, low complexity (AC:L) applies, though no fresh public POC for this specific path was provided.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 23, 2026

Authenticated attackers with nothing more than a Subscriber-level account can delete arbitrary business listings - including listings owned by other users - on WordPress sites running the Directorist directory/classifieds plugin from version 3.1.0 up to (but not including) 8.9.5. The root cause is a listing-deletion code path that does not verify ownership, a route that the earlier fixes for CVE-2023-1889 and CVE-2023-35052 failed to close, making this an incomplete-fix regression rather than a novel bug class. Scoring 6.5 under CVSS 3.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N), the issue is purely an integrity problem with no confidentiality loss and no availability impact, and no public exploit code has been identified at time of analysis. Exposure is highest on directory and classified-ad sites that leave WordPress 'Anyone can register' enabled, since a self-registered Subscriber is sufficient to weaponize the flaw.

RemediationAI

Upgrade Directorist to 8.9.5 or later - vendor-released patch: 8.9.5 - which closes the previously unaddressed deletion path; because this is an incomplete fix of CVE-2023-1889 and CVE-2023-35052, administrators who already applied those earlier patches must still update, and site owners running heavily customized or forked deletion logic should audit every code path that removes a listing for a missing ownership/capability check rather than assuming the update covers bespoke handlers. Where immediate upgrading is not possible, the most effective compensating control is to eliminate the prerequisite account: set WordPress Settings > General > Membership to disallow 'Anyone can register', and remove the Subscriber role from any self-service onboarding flow - the trade-off is loss of organic user sign-ups, which is significant for directory and classified sites that rely on contributor registrations. As a secondary measure, restrict who can create listings at all (require Editor/Author-level approval), or temporarily disable the front-end listing-management/delete UI via capability filters, accepting the loss of legitimate self-service deletion by listing owners. A WAF rule or reverse-proxy filter that blocks authenticated requests targeting the plugin's listing-deletion AJAX/REST action from accounts lacking elevated roles can add interim protection, but such rules are brittle against action-name changes and should be treated as a stopgap, not a fix. Monitor the WPScan advisory at https://wpscan.com/vulnerability/b5f83718-84ff-49e4-9ad7-395cc0ab494b/ and the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-84098 for any revision; note that no public exploit code has been identified at time of analysis, so this is a moderate-priority integrity issue rather than an emergency patching scenario.

Affected VersionsENISA

Directorist: AI-Powered Business Directory, Listings & Classified Ads 3.1.0 <8.9.5

Affected Packages

euvd directorist_ai_powered_business_directory_listings_classified_ads fix: 8.9.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is a WordPress plugin - Directorist: AI-Powered Business Directory, Listings & Classified Ads - which persists listings as a custom post type and exposes create/edit/delete operations through AJAX and/or REST handlers. The vulnerability class is CWE-863 (Incorrect Authorization): the vulnerable deletion handler authenticates the request (a valid logged-in session is required) but never performs the corresponding authorization check, i.e. it fails to confirm that the requesting user is the listing's author or holds a role permitted to remove it. WordPress plugins of this type normally pair a nonce check with a capability check such as current_user_can(), and directory plugins additionally need an ownership comparison against the listing's post_author. The prior advisories CVE-2023-1889 and CVE-2023-35052 addressed one such deletion vector, but a second, parallel deletion path remained reachable from at least version 3.1.0 through the entire release history before 8.9.5, so any deployment on that range should be treated as still vulnerable regardless of whether the earlier patches were applied. Because the vulnerability sits in server-side authorization logic rather than memory handling or parsing, exploitation is deterministic and requires no user interaction, no non-default plugin configuration, and no elevated privileges - only a single valid low-privilege account.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (wpscan) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 6.5 MEDIUM

Network-reachable REST/AJAX path (AV:N), low complexity reusing known 2023 technique (AC:L), needs a Subscriber account (PR:L), no interaction; arbitrary listing deletion is high integrity (I:H) with no confidentiality or service-availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (wpscan).

CVSS VectorVendor: wpscan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

4
CVSS changed
Sep 23, 2026 - 11:22 NVD
6.5 (MEDIUM)
Patch available
Sep 23, 2026 - 07:01 EUVD
CVE Published
Sep 23, 2026 - 06:17 cve.org
MEDIUM 6.5
CVE Published
Sep 23, 2026 - 06:17 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Directorist: AI-Powered Business Directory, Listings & Classified Ads WordPress plugin before 8.9.5 does not properly verify a listing's ownership before deleting it, allowing authenticated attackers with Subscriber-level access and above to delete arbitrary listings, including ones belonging to other users.

This is an incomplete fix of CVE-2023-1889 / CVE-2023-35052: a separate, unaddressed listing-deletion path allows the same impact, from at least version 3.1.0 through the current release.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Medium
popular WordPress directory/classifieds plugin, roughly 100k+ active installs
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy