Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach unauthenticated upload endpoint
-
ExploitSubmit crafted file-write request
-
ExecutionWrite arbitrary content to chosen path
-
ImpactOverwrite or plant target file
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No authentication, user interaction, or special configuration is required to reach the flaw: the plugin exposes an upload handler that does not restrict file type or destination to unauthenticated callers, so any default install of WP-BusinessDirectory ≤4.0.2 is exploitable remotely. The decisive LIMITING factor, stated by the vendor, is that arbitrary file write does NOT translate to code execution on a default server configuration - achieving RCE would require a non-default/misconfigured server (e.g., writable, executable web paths) or chaining with another weakness. Exploitation also requires that the vulnerable plugin be installed and active and that the upload endpoint be network-reachable. |
| Impact | This is a moderate-severity issue that should be patched but does not rank as a drop-everything emergency on the available signals. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, base 5.3) indicates remote, low-complexity, unauthenticated exploitation with no user interaction - attractive characteristics - but the rated impact is limited to partial integrity (I:L) with no confidentiality or availability effect. No EPSS score, CISA KEV entry, POC reference, or SSVC decision data was supplied in the input, so exploitation-probability and automatability signals are simply absent rather than low; absence is not evidence of safety. The single most important tempering factor is stated in the description itself: the handler allows arbitrary file write but 'not to execute code on a default server configuration,' which caps the primary vector (RCE via webshell) unless the environment is misconfigured or the write is chained with another weakness. In my judgment the input CVSS under-rates the integrity impact - writing arbitrary content to arbitrary locations by an unauthenticated attacker is a strong integrity compromise (file overwrite, data planting) rather than the 'low' the vector claims - see assessed_cvss_vector. Net: a genuine, remotely reachable unauthenticated flaw worth prioritizing for any site running this plugin, but its real-world blast radius is constrained by the no-default-RCE caveat and the plugin's limited deployment footprint. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker locates a site running WP-BusinessDirectory ≤4.0.2 and sends a crafted request to the plugin's unvalidated upload handler, writing a file with attacker-chosen content to an attacker-chosen path. On a default server this does not yield code execution, but the attacker can overwrite existing files (e.g., clobber or tamper with site assets/content) or stage a payload for later chaining. No public exploit is identified in the provided data, so exploitation would require independent development against the known handler. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Unauthenticated arbitrary file upload in the WP-BusinessDirectory WordPress plugin (through version 4.0.2) allows remote attackers to write files with attacker-controlled content to attacker-chosen locations on the web server. Any default installation running the vulnerable plugin with the upload endpoint reachable is exposed without credentials or user interaction, but the plugin vendor notes that this arbitrary write does not translate into code execution on a default server configuration - achieving remote code execution requires a non-default or misconfigured server (for example, writable and executable web paths) or chaining with a second weakness. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV); this is a moderate-severity integrity issue that warrants patching but is not a drop-everything emergency on the available signals.
RemediationAI
No vendor-released patch was identified at time of analysis for CVE-2026-89271, so the immediate priority is removal or disabling of the vulnerable component: deactivate and delete the WP-BusinessDirectory plugin (or replace it with an actively maintained alternative) on any site where it is not strictly required, and treat the affected upload endpoint as untrusted until an update is published. Where the plugin must remain live, apply targeted compensating controls and accept their trade-offs: block or rate-limit unauthenticated requests to the plugin's upload actions - typically /wp-admin/admin-ajax.php with plugin-specific action parameters, and any plugin-specific admin-post or REST routes - using a WAF rule or web-server location block (side effect: legitimate front-end form submissions that rely on the same endpoint may break, so test against real traffic); enforce WordPress-level upload restrictions such as DISALLOW_UNFILTERED_HTML and strict MIME/extension filtering, and ensure the uploads directory is mounted non-executable (php_admin_flag engine off / deny execution of .php under wp-content/uploads) so that any dropped file cannot be run (side effect: none for well-behaved sites, but this only removes the RCE path, not the write capability); and restrict filesystem write permissions on the web root so the web-server user cannot create files outside wp-content/uploads. Monitor the WPScan entry (https://wpscan.com/vulnerability/78b3ade9-1614-4040-87be-c43dbc50b79e/) and the NVD record (https://nvd.nist.gov/vuln/detail/CVE-2026-89271) for a fixed release, and in the interim audit host file systems for unexpected files in web-accessible directories as a detection measure, since patched-version confirmation is not yet available.
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 flaw is an instance of CWE-434 (Unrestricted Upload of File with Dangerous Type) in a WordPress plugin. WordPress plugins commonly expose file-handling routines through admin-ajax.php or admin-post.php handlers, and unauthenticated access is enabled when a handler is registered for the non-privileged (nopriv) action path. Here the handler does not validate either the file type/extension of the uploaded content or the destination directory it is written to, so an unauthenticated caller can dictate both the payload and the path it lands in. The practical significance of that capability is bounded by server configuration: on a hardened/default stack, uploaded files are not directly executable via the web server, so the impact is limited to file-system integrity, potential defacement, content injection, disk consumption, or as a staging step for a later chain. The assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N reflects full network reachability, low complexity, no privileges or interaction required, and high integrity impact with no confidentiality or availability impact; note this differs from the NVD/vendor-published 5.3 score (C:N/I:L/A:N), which weights the write capability more conservatively on the assumption of a default, non-executable configuration. No CPE strings were supplied with the input data; affected version scope is taken from the EUVD record (WP-BusinessDirectory 0 through 4.0.2).
Know when WordPress 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:N/UI:N/S:U/C:N/I:L/A:N
Unauthenticated remote write of arbitrary content to arbitrary paths is a full integrity compromise (I:H), not partial; no confidentiality and, absent default RCE, no direct availability impact.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
3DescriptionCVE.org
The WP-BusinessDirectory WordPress plugin through 4.0.2 does not restrict the type or destination of files saved by an unauthenticated upload handler, allowing unauthenticated attackers to write files with arbitrary content to arbitrary locations, though not to execute code on a default server configuration.
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
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-98300
GHSA-mr4c-8644-ggh2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB