Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain subscriber account
-
DeliveryAuthenticate to WordPress REST API
-
ExploitCall order-creation endpoint lacking capability check
-
ExecutionForge paid order/payment with arbitrary amount
-
PersistAttribute record to another user
-
ImpactCorrupt billing/payment integrity
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
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 subscriber role or above (PR:L), so the site must permit self-registration or the attacker must otherwise obtain a low-privilege account - a common default for directory/classifieds sites. The target must run Directorist versions 8.9.1 through before 8.9.5 with its order/payment (paid-listing monetization) functionality in use for the forged records to be meaningful. No user interaction, no admin privileges, and no non-default configuration beyond having paid orders enabled are needed; exploitation is remote over the WordPress REST API with low complexity. Impact is limited to integrity (fraudulent order/payment records and misattribution) - no confidentiality or availability impact. |
| Impact | This is a genuine but moderate-priority issue, not an inflated high-CVSS finding. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, base 4.3) is internally consistent and correctly scoped to integrity-only: an authenticated low-privilege user (subscriber, PR:L) can remotely and easily (AC:L, no UI) abuse a REST endpoint that fails CWE-862 capability checks, creating paid order and payment records with arbitrary amounts attributed to other users. No CVSS conflict is present - network vector matches a WordPress REST API, and the low privilege requirement matches the described subscriber-role prerequisite. There is no EPSS score, no CISA KEV listing, and no public POC provided, so exploitation status is 'no public exploit identified at time of analysis.' The impact is business-logic/data-integrity fraud (fake billing/payment records, financial-record pollution, attribution to arbitrary users) rather than data theft or code execution, which correctly bounds severity to Medium/Low. Real-world priority: patch on a normal cycle for sites that allow open subscriber registration and use Directorist's paid-listing/monetization features; sites without paid orders or public self-registration face materially lower risk. The 'Authentication Bypass' tag overstates the class - this is a broken-access-control/authorization defect, not authentication bypass - so decisions should be driven by the CWE-862 authorization framing, not the tag. |
| Exploit ScenarioDerived | An attacker self-registers a free subscriber account on a Directorist-powered site (registration is commonly open) and calls the plugin's order-creation REST API directly, which never verifies the caller's capability. They forge paid order and payment records with attacker-chosen amounts and assign them to other user accounts - enabling billing/payment-record fraud, financial data pollution, or making another user appear to have paid. No public exploit code is available at time of analysis, but the flaw is trivially reachable given the low complexity and network vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Authenticated users holding only the WordPress subscriber role - or any higher role - can forge paid order and payment records with arbitrary amounts and assign them to other accounts in the Directorist WordPress plugin (AI-Powered Business Directory, Listings & Classified Ads) versions 8.9.1 through before 8.9.5. The REST API order-creation endpoint performs no capability check, so any logged-in low-privilege account on a site that permits self-registration (a common configuration for directory and classifieds sites) can inject fraudulent billing and payment data, resulting in integrity-only impact with no confidentiality or availability loss. This is a moderate, genuine authorization gap rather than a high-severity compromise: there is no public exploit identified at time of analysis, no confirmed active exploitation (CISA KEV), and the vendor has released a fix in version 8.9.5.
RemediationAI
Vendor-released patch: upgrade Directorist to version 8.9.5 or later; because WordPress plugins auto-update only if configured, verify the installed version and apply the update manually via the WordPress admin or WP-CLI if auto-updates are disabled. If immediate upgrade is impossible, reduce exposure by disabling self-registration and denying subscriber-level accounts (so only trusted roles remain), though this breaks open directory/classifieds workflows that rely on public sign-ups; alternatively disable the plugin's paid-order/payment functionality entirely, which removes the exposure but also disables monetization; and add a WAF or reverse-proxy rule restricting POST access to the plugin's REST order/payment routes to trusted administrative sessions, recognizing that legitimate front-end checkout flows may break. After patching or mitigating, audit existing order and payment records for anomalous amounts or entries attributed to unexpected users, since fraudulent records may already exist undetected. Consult the WPScan advisory at https://wpscan.com/vulnerability/dff1eca0-3fdd-4e7f-8ad2-1fa52b3b4a80/ and the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-84027 for the latest patch and detail updates.
Affected VersionsENISA
Affected Packages
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 root cause is CWE-862 (Missing Authorization) in the WordPress REST API implementation of the Directorist plugin, which powers business directory, listing, and classified-ad monetization. WordPress REST routes are registered with permission callbacks; when a callback only verifies that a request is authenticated (or omits the check entirely) instead of validating a capability such as current_user_can(), any logged-in account - including the default subscriber role - can invoke privileged functionality. Here the order/payment creation route accepts client-supplied amount and user-attribution parameters without verifying that the caller is permitted to create orders or act on behalf of another user, enabling both parameter tampering (arbitrary order/payment amounts) and misattribution of those records to arbitrary accounts. The plugin is a third-party WordPress extension rather than core WordPress, so exposure depends on the site running an affected Directorist build with paid-listing/order functionality enabled; the attack is remote over HTTP against the WordPress REST API with low complexity, requiring only a valid low-privilege session and no user interaction.
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
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Remote REST API abuse by an authenticated subscriber (PR:L) with no UI; integrity-only impact from forged order/payment records (I:L), no confidentiality or availability effect.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Directorist: AI-Powered Business Directory, Listings & Classified Ads WordPress plugin before 8.9.5 does not check user capabilities when creating orders through its REST API, allowing users with the subscriber role and above to create paid order and payment records with arbitrary amounts and attribute them to other users.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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
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
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
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
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
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
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-85033
GHSA-cq43-6mf7-3fqw
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB