Samker's Computer Forum - SCforum.info

World TOP Headlines: => Latest Security News & Alerts => Topic started by: Pez on 09. March 2016., 00:58:33

Title: A Backdoored WordPress Plugin and 3 Additional Vulnerabilities
Post by: Pez on 09. March 2016., 00:58:33
A Backdoored WordPress Plugin and 3 Additional Vulnerabilities

We have several plugin vulnerabilities we’d like to bring to your attention this week.

First up is a backdoor that was added to the Custom Content Type (https://wordpress.org/plugins/custom-content-type-manager/) Manager plugin. The backdoor was added by a malicious coder who gained access to the plugin code in the official WordPress plugin repository.

It’s unclear whether the plugin author’s credentials were stolen or whether the malicious actor was granted access. The WordPress security team removed the malicious user account that added the backdoor to the plugin. They have also removed all malicious code  (https://wordpress.org/plugins/custom-content-type-manager/changelog/)that was added to the plugin and updated the version number so that users running this plugin will be prompted to upgrade.

If you are using Custom Content Type Manager, you will need to take the following steps to remove any infection and install the updated non-backdoored version of the plugin.

1. Update to version 0.9.8.9 of Custom Content Type Manager (https://wordpress.org/plugins/custom-content-type-manager/)
2. The malicious code in this plugin installed a backdoor in WordPress core files. So run a Wordfence scan (https://wordpress.org/plugins/wordfence/) on your site to check the integrity of your core files. The free version of Wordfence will do this.  Make sure the option to compare your core files against the official WordPress versions is enabled (https://docs.wordfence.com/en/Wordfence_options#Scan_core_files_against_repository_version_for_changes). In the scan results, make sure that the following three files are not modified. ◦wp-login.php
◦wp-admin/user-edit.php
◦wp-admin/user-new.php

3. If any of the above files are modified, you can use Wordfence to repair them.
4. Change the passwords of all your users.
5. Delete any user accounts you don’t recognize. Check admin accounts in particular.
6. If a file called wp-options.php exists in your home directory, remove it.

The SP Projects and Document Manager (https://wordpress.org/plugins/sp-client-document-manager/) plugin  version 2.5.9.6 has multiple vulnerabilities including file upload (http://www.securityfocus.com/archive/1/537705/30/0/threaded), code execution, sql injection and XSS. Update to to version 2.6.1.1 immediately which contains the vendor released fixes (https://wordpress.org/plugins/sp-client-document-manager/changelog/) and is the newest version.

If you are running Easy Digital Downloads (https://wordpress.org/plugins/easy-digital-downloads/), ensure you’ve updated to at least version 2.5.8 which fixes an object injection vulnerability (https://github.com/easydigitaldownloads/Easy-Digital-Downloads/commit/7e83d2737b430c76f515b5433ee067fa5e6b1d4f). The current version is 2.5.9 (https://wordpress.org/plugins/easy-digital-downloads/changelog/). The vulnerability was disclosed within the past week.

A vulnerability was publicly disclosed (http://www.securityfocus.com/archive/1/537681/30/0/threaded) in the Bulk Delete plugin (https://wordpress.org/plugins/bulk-delete/) earlier this month that allows unprivileged users to delete pages or posts. The vendor has already released a fix so make sure that if you’re using the Bulk Delete Plugin, you’ve updated to version 5.5.4 (https://wordpress.org/plugins/bulk-delete/changelog/) which is the latest version.

That concludes our vulnerability roundup for this week. Please share this with the larger WordPress community to help create awareness of these issues.


Original article: https://www.wordfence.com/blog/2016/03/backdoored-wordpress-plugin-vuln-roundup/?utm_source=list&utm_medium=email&utm_campaign=bdr1 (https://www.wordfence.com/blog/2016/03/backdoored-wordpress-plugin-vuln-roundup/?utm_source=list&utm_medium=email&utm_campaign=bdr1)