Hi Para-Noid,
There is more than meets the eye at first glance, insecurity that is, also for that PHP version: PHP/5.4.45 - for instance:
https://www.exploit-db.com/exploits/38123/Cookies not flagged as "HttpOnly" may be read by client side script and are at risk of being interpreted by a cross site scripting (XSS) attack. Whilst there are times where a cookie set by the server may be legitimately read by client script, most times the "HttpOnly" flag is missing it is due to oversight rather than by design.
Result
It looks like 3 cookies are being set without the "HttpOnly" flag being set (name : value):
60gpBAK : R122xxx0331
60gp : R41xxx556706
clef_wp_session : cb124478ec065b4df610xxxxxxxxxx0%7C%7C2950605630%7C%7C1459532655
Unless the cookie legitimately needs to be read by JavaScript on the client, the "HttpOnly" flag should always be set to ensure it cannot be read by the client and used in an XSS attack.
WordPress Outdated WordPress Version
4.2.7
Version does not appear to be latest 4.4.2 - update now.
he following plugins were detected by reading the HTML source of the WordPress sites front page.
q2w3-fixed-widget 4.0.6 latest release (4.0.6)
http://www.q2w3.ru/q2w3-fixed-widget-wordpress-plugin/wpclef 2.1.1 latest release (2.4.1) Update required
http://wordpress.org/extend/plugins/wpclefdownload-manager latest release (2.8.93)
http://www.wpdownloadmanager.com/purchases/contextual-related-posts latest release (2.2.3)
https://webberzone.com/plugins/contextual-related-posts/cookie-law-info 1.5.3 latest release (1.5.3)
http://wordpress.org/extend/plugins/cookie-law-info/description/wysija-newsletters 2.6.16 latest release (2.7.1) Update required
http://www.mailpoet.com/wp-downloadmanager 1.62 latest release (1.67) Update required
http://lesterchan.net/portfolio/programming/php/Plugins are a source of many security vulnerabilities within WordPress installations, always keep them updated to the latest version available and check the developers plugin page for information about security related updates and fixes.
Warning User Enumeration is possible
The first two user ID's were tested to determine if user enumeration is possible.
ID User Login
1 None admin
2 None
It is recommended to rename the admin user account to reduce the chance of brute force attacks occurring. As this will reduce the chance of automated password attackers gaining access. However it is important to understand that if the author archives are enabled it is usually possible to enumerate all users within a WordPress installation.
Warning Directory Indexing Enabled
In the test we attempted to list the directory contents of the uploads and plugins folders to determine if Directory Indexing is enabled. This is an information leakage vulnerability that can reveal sensitive information regarding your site configuration or content.
/wp-content/uploads/ enabled
/wp-content/plugins/ disabled
Directory indexing was tested on the /wp-content/uploads/ and /wp-content/plugins/ directores. Note that other directories may have this web server feature enabled, so ensure you check other folders in your installation. It is good practice to ensure directory indexing is disabled for your full WordPress installation either through the web server configuration or .htaccess.
Website owner should also hire someone to configure WordPress CMS correctly and in the first place keep it fully updated (also plug-ins)
polonus (volunteer website security analyst and website error-hunter)
