CVE-2026-6070
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP-BusinessDirectory plugin for WordPress is vulnerable to Unauthenticated Arbitrary File Deletion in versions up to and including 4.0.1. This is due to insufficient path validation in the remove() method of the JBusinessDirectoryControllerUpload class. The task=upload.remove endpoint is accessible without authentication via the plugin's frontend routing system. The _filename parameter is accepted with RAW filter (no sanitization), and the helper function makePathFile() only normalizes directory separator characters without stripping path traversal sequences (../). When combined with the _path_type=2 parameter, which sets the base directory to the plugin's site folder, an attacker can supply a _filename value containing ../ sequences to traverse outside the plugin directory and call PHP's unlink() on arbitrary files — including wp-config.php, wp-config-backup.php, or other critical server files accessible to the web server process. This makes it possible for unauthenticated attackers to delete arbitrary files on the server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP-BusinessDirectory plugin for WordPress up to version 4.0.1 contains an unauthenticated arbitrary file deletion vulnerability in the JBusinessDirectoryControllerUpload class. The remove() method accepts the _filename parameter without sanitization via a RAW filter, and the makePathFile() helper fails to strip path traversal sequences (../). Combined with the _path_type=2 parameter that sets the base directory, attackers can traverse outside the plugin directory and delete critical files like wp-config.php via PHP's unlink() function.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WP-BusinessDirectory plugin installation and versionAccess WordPress admin panel, navigate to Plugins > Installed Plugins, locate WP-BusinessDirectory (or Business Directory Plugin) and read the version number from the plugin description. Alternatively, inspect the plugin main PHP file (typically /wp-content/plugins/wp-business-directory/ or /wp-content/plugins/business-directory-plugin/) and search for a version constant or 'Version:' comment in the file header.Affected if The plugin is installed and the reported version is 4.0.1 or lower (any version up to and including 4.0.1).
-
Confirm plugin is active and the vulnerable controller existsVerify the plugin status shows 'Active' in the WordPress plugins admin page. Then locate the vulnerable controller file: typically at /wp-content/plugins/[business-directory]/controllers/upload.php or /controllers/JBusinessDirectoryControllerUpload.php and confirm the file exists.Affected if The plugin is active and the upload controller file with the remove() method is present on the server.
-
Check for evidence of exploitationInspect the web server access logs for requests containing 'task=upload.remove' combined with '../' path traversal sequences in the _filename parameter (e.g., ?task=upload.remove&_filename=../../../wp-config.php&_path_type=2). Also check if wp-config.php or other critical files have been recently modified or deleted.Affected if Log analysis reveals suspicious requests to the upload.remove endpoint with path traversal patterns, or critical WordPress files (wp-config.php, .htaccess) are missing or recently modified without authorized action.
You are affected if WP-BusinessDirectory plugin version 4.0.1 or lower is installed and active, with the vulnerable upload controller present and the endpoint accessible (which it is by default for unauthenticated users).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to a version beyond 4.0.1 which contains proper path sanitization; alternatively, implement input validation in the _filename parameter to strip path traversal sequences (../) before use in the makePathFile() function.
Latest version beyond 4.0.1 (check WordPress plugin repository for current stable release)
- 1. Update the WP-BusinessDirectory plugin to the latest available version from the WordPress plugin repository
- 2. After updating, verify that the remove() method in JBusinessDirectoryControllerUpload class has proper path sanitization
- 3. Confirm that the _filename parameter now strips path traversal sequences (../) before processing
- 4. Test that authenticated users can still manage uploads as expected post-update
- 5. Review server logs for any exploitation attempts prior to the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6070 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data