WP-DBManager <= 2.79.1 - Directory Traversal Allowing Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 2.79.2
- Affected Plugin
- WP-DBManager
- Affected Version
< 2.79.2- CVSS
- 8.7High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP-DBManager WordPress plugin, affecting versions < 2.79.2. It carries a CVSS score of 8.7 (reachable over the network; low attack complexity; high integrity, availability impact). The issue is fixed in version 2.79.2; sites on affected versions should update now. Disclosed October 2018, reported by RIPS Technologies.
Vulnerability Overview
The WP-DBManager plugin for WordPress is vulnerable to Directory Traversal allowing arbitrary file deletion in versions up to, and including, 2.79.1. This allows authenticated high-privilege attackers to delete arbitrary files, which can be used to reset a site and gain administrative access.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in WP-DBManager < 2.79.2 takes a caller who can reach the endpoint. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For WP-DBManager the fix is 2.79.2: builds < 2.79.2 are affected, anything from 2.79.2 onward is not.
Remediation
Update to version 2.79.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP-DBManager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP-DBManager 2.79.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C