Wp Dbmanager: A security weakness
Wp Dbmanager is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Wp Dbmanager
- Plugin slug
wp-dbmanager- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jan 05, 2018
This CVE was published Jan 05, 2018 and is one of 4 known issues for this plugin.
Update, patch or deactivate.
Update Wp Dbmanager to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
(1) wp-dbmanager.php and (2) database-manage.php in the WP-DBManager (aka Database Manager) plugin before 2.7.2 for WordPress place credentials on the mysqldump command line, which allows local users to obtain sensitive information by listing the process.
NVD vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary and upstream sources
- NVD record for CVE-2014-8335
- Upstream reference packetstormsecurity.com
- Upstream reference openwall.com
- Upstream reference vapid.dhs.org
- Upstream reference exchange.xforce.ibmcloud.com
- GitHub upstream reference github.com
- WordPress.org plugin page wordpress.org
- Upstream reference packetstormsecurity.com
- Upstream reference openwall.com
- Upstream reference vapid.dhs.org
- Upstream reference exchange.xforce.ibmcloud.com
- GitHub upstream reference github.com
- WordPress.org plugin page wordpress.org