A vulnerability classified as problematic has been found in WP-DBManager up to 2.7.1 on WordPress (WordPress Plugin). This affects some unknown functionality of the file wp-dbmanager.php of the component Database Manager. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:

(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.

The bug was discovered 10/16/2014. The weakness was presented 01/05/2018 (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2014-8335 since 10/20/2014. An attack has to be approached locally. A authentication is required for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 1177 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:wp-dbmanager.php it is possible to find vulnerable targets with Google Hacking. The commercial vulnerability scanner Qualys is able to test this issue with plugin 13068 (WordPress WP-DBManager plugin Remote Command Injection Vulnerability).

Upgrading to version 2.7.2 eliminates this vulnerability.

Productinfo

Type

• WordPress Plugin

Name

• WP-DBManager

Version

• 2.7.0
• 2.7.1

License

• open-source

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion