Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account on WordPress site
-
DeliveryIdentify object ID parameter in Business Directory request
-
ExploitSubstitute another user's object ID
-
ExecutionServer authorizes by ID not ownership
-
ImpactModify or disrupt victim's directory records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires an authenticated WordPress account at Contributor level or higher on a site running the Business Directory plugin version 6.4.27 or earlier (PR:L). No user interaction is needed (UI:N) and the attack is performed remotely over the network (AV:N) with low complexity (AC:L) by tampering with a direct object reference (an ID parameter) so the application returns or alters records belonging to another user. The primary limiting factor is the need for a valid low-privilege account, which excludes purely anonymous internet attackers; impact is bounded to low integrity and availability effects with no confidentiality loss (C:N/I:L/A:L). |
| Impact | This is a moderate-severity, low-real-risk issue based on the balance of signals. The CVSS 3.1 base score is 5.4 (Medium) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L, meaning network-reachable and low-complexity but requiring authenticated privileges (PR:L, mapped to WordPress Contributor role) and yielding only low integrity and availability impact with no confidentiality loss. No EPSS score, no CISA KEV listing, and no public proof-of-concept were provided, so exploitation status is 'no public exploit identified at time of analysis.' The requirement for a valid Contributor account substantially narrows the realistic attacker population versus a fully unauthenticated flaw, and the C:N/I:L/A:L impact profile indicates limited blast radius (an IDOR letting an authenticated user manipulate objects they should not, rather than mass data theft or takeover). No signals conflict here - all point to a genuine-but-low-priority vulnerability. Priority is driven mainly by the plugin's install base rather than by exploitation urgency; absent KEV/EPSS/POC this does not warrant emergency patching, but it should be remediated in normal maintenance cycles. |
| Exploit ScenarioDerived | An attacker who has registered or obtained a WordPress Contributor account on a site running Business Directory <= 6.4.27 crafts requests referencing object identifiers (e.g., directory listing or record IDs) belonging to other users, and because access is keyed on the supplied ID rather than ownership, they view or modify records they do not own. No public proof-of-concept was provided, and the low-complexity network vector (AC:L/AV:N) means the manipulation is a simple parameter change once authenticated. Impact is limited to low integrity/availability effects (I:L/A:L), such as tampering with or disrupting other users' directory entries. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Insecure direct object reference in the Business Directory WordPress plugin, affecting versions up to and including 6.4.27, lets an authenticated Contributor-level account manipulate an object identifier so the plugin returns or modifies directory records belonging to another user. The issue rates CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L, CWE-639): remote and low complexity, but gated on holding a valid low-privilege WordPress account (Contributor or higher), which excludes purely anonymous attackers, with impact bounded to low integrity and availability effects and no confidentiality loss. Exploitation status: no public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
RemediationAI
No vendor-released patch version is confirmed in the available data - the supplied advisory and CPE record pin the affected range at 6.4.27 and earlier but do not name a fixed release - so administrators should monitor the Business Directory plugin changelog and the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/business-directory-plugin/vulnerability/wordpress-business-directory-plugin-6-4-27-insecure-direct-object-references-idor-vulnerability?_s_id=cve, and update to the first release published after 6.4.27 once it is confirmed to contain the authorization fix. Because exploitation requires an authenticated account at Contributor level or higher (PR:L), the highest-value compensating control is account hygiene: audit the site's user list, remove or downgrade dormant Contributor and higher accounts, and restrict self-registration or role-assignment plugins that could hand an attacker the required account level - the trade-off is purely operational, since it does not remove the flaw itself. Where Contributor access is broadly granted and cannot be trimmed, consider temporarily deactivating Business Directory until a patched version is available, accepting the loss of directory functionality, or deploying virtual patching / a WAF rule that blocks requests tampering with the plugin's object-ID parameters while monitoring for repeated 403s generated by such a rule, which risks false positives against legitimate listing edits. Sites able to modify code can also add an ownership check so record operations derive the object owner from the current user rather than from the submitted identifier; this is an upstream fix (patch/commit style) and a supported fixed release is not independently confirmed from the data provided.
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
Business Directory is a WordPress plugin maintained by the Strategy11 Team and distributed through the WordPress plugin ecosystem; the CPE cpe:2.3:a:strategy11_team:business_directory:*:*:*:*:*:*:*:* maps the affected product family. The root cause class is CWE-639, Authorization Bypass Through User-Controlled Key (commonly called IDOR): instead of deriving the target record from the authenticated session and enforcing an ownership or capability check, the plugin trusts an identifier supplied by the client when fetching or updating a directory listing. Because the check is missing rather than the key being guessable, any user who can reach the vulnerable action can substitute an identifier for an object they do not own. In the WordPress capability model this matches the Contributor role referenced in the description and the PR:L component of the CVSS vector; the attacker must already hold such an account, but needs no interaction from the victim (UI:N) and can act entirely over the network (AC:L). The assessed impact is deliberately narrow - C:N/I:L/A:L - meaning tampering can alter or disrupt the availability of other users' records but does not expose their data. This is distinct from an authentication bypass in the strict sense: authentication is required, and what fails is the per-object authorization decision.
Know when Business Directory 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:L
Contributor account required (PR:L), remote low-complexity IDOR (AV:N/AC:L/UI:N); impact limited to low integrity and availability with no confidentiality per the description and vector.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Contributor Insecure Direct Object References (IDOR) in Business Directory <= 6.4.27 versions.
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
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Business Directory
View allThe Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Blind SQL injection in WPTasty Business Directory plugin versions through 6.4.27 allows an authenticated attacker with h
The Business Directory Plugin plugin for WordPress is vulnerable to CSV Injection in versions up to, and including, 6.4.
Unauthenticated XSS in the Business Directory WordPress plugin (versions ≤ 6.4.25, by Strategy11 Team) permits remote at
Stored Cross-Site Scripting in the Business Directory WordPress plugin (versions up to and including 6.4.24) allows auth
Broken access control in Business Directory WordPress plugin versions 6.4.26 and earlier exposes unauthenticated endpoin
Unauthenticated IDOR in the Business Directory WordPress plugin (versions <= 6.4.26) allows remote attackers to access o
Broken Access Control in the Business Directory WordPress plugin (versions 6.4.23 and below) permits unauthenticated rem
Cross-site scripting in the Business Directory WordPress plugin (versions 6.4.22 and earlier) allows authenticated subsc
Unauthenticated cross-site scripting in the Business Directory WordPress plugin (versions <= 6.4.22) allows remote attac
Cross-Site Request Forgery (CSRF) vulnerability in Business Directory Team Business Directory Plugin - Easy Listing Dire
EUVD-2026-89841
GHSA-cq3j-wj6g-q93r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB