| CVE | CVE-2026-6070 |
|---|---|
| CVSS | 9.1 (Critical) |
| Publicly Published | June 30, 2026 |
| Last Updated | July 1, 2026 |
| Researcher |
Nabil Irawan
- Heroes Cyber Security
|
The 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.
| Software Type | Plugin |
|---|---|
| Software Slug | wp-businessdirectory (view on wordpress.org) |
| Patched? | Yes |
| Remediation | Update to version 4.0.2, or a newer patched version |
| Affected Version |
|
| Patched Version |
|
| # | Title | CVE ID | CVSS | Researchers | Date |
|---|---|---|---|---|---|
| 1 | WP-BusinessDirectory – Business directory plugin for WordPress <= 4.0.0 - Authenticated (Subscriber+) Arbitrary File Upload | CVE-2026-39591 | Jarno Vos (jarnovos) | April 8, 2026 | |
| 2 | WP-BusinessDirectory <= 3.1.5 - Reflected Cross-Site Scripting | CVE-2025-68887 | Nguyen Xuan Chien | December 30, 2025 | |
| 3 | WP-BusinessDirectory <= 3.1.4 - Unauthenticated SQL Injection | CVE-2025-24759 | Martino Spagnuolo | July 11, 2025 | |
| 4 | WP-BusinessDirectory <= 3.1.2 - Reflected Cross-Site Scripting | CVE-2025-32630 | LVT-tholv2k | April 10, 2025 | |
| 5 | WP-BusinessDirectory <= 3.1.2 - Unauthenticated Arbitrary File Deletion | CVE-2025-32629 | LVT-tholv2k | April 9, 2025 |
This record contains material that is subject to copyright.
Copyright 2012-2026 Defiant Inc.
License: Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy. Read more.
Copyright 1999-2026 The MITRE Corporation
License: CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy. Read more.
Have information to add, or spot any errors? Contact us at wfi-support@wordfence.com so we can make any appropriate adjustments.
Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!
Learn moreWant to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.
The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.
Documentation