Do not know what avast flags at the moment, we should hear that from an Avast Team Member.
As we are volunteers with relevant info, we cannot fill yoiu in with the details.
Anyway you have several serious security issues on the website that should be mitigated a.s.a.p.
Your CMS version is outdated: Web application details:
Application: WordPress - http://www.wordpress.org
Web application version:
WordPress version: WordPress
Wordpress Version 4.4 based on: -http://www.ews-o.com/wp-admin/js/common.js
WordPress theme: -http://test.ews-o.com/live/wp-content/themes/ews5/
WordPress version outdated: Upgrade required.
Outdated WordPress Found: WordPress Under 4.5
WordPress Plugins
The following plugins were detected by reading the HTML source of the WordPress sites front page.
wp-retina-2x 4.4.4 latest release (4.5.5) Update required
http://apps.meow.fr
disqus-comment-system 2.84 latest release (2.85) Update required
https://disqus.com/
respondjs 1.4.2 latest release (1.4.2)
http://www.ramoonus.nl/wordpress/respondjs/
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 Robin robin-admin
2 SEO EWS seo-admin
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.
The following jQuery libraries are to be retired (zipfile for later reference): http://retire.insecurity.today/#!/scan/d60e90b67ede1dc38df03cbdfbeb77f16d5aef075d30ecd0f827d8ef096ac13c
Your server is giving away excessive header info: Apache/2.2.15 (CentOS)
14 SRI insecurity issues here (no SRI hashes): https://sritest.io/#report/9b10789e-1bf4-48ae-ac52-70b247861bf5
Same meagre F-Status for header security: https://securityheaders.io/?q=http%3A%2F%2Fwww.ews-o.com&followRedirects=on
Missing Headers
Content-Security-Policy Content Security Policy is an effective measure to protect your site from XSS attacks. By whitelisting sources of approved content, you can prevent the browser from loading malicious assets.
X-Frame-Options X-Frame-Options tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. Recommended value “x-frame-options: SAMEORIGIN”.
X-XSS-Protection X-XSS-Protection sets the configuration for the cross-site scripting filter built into most browsers. Recommended value “X-XSS-Protection: 1; mode=block”.
X-Content-Type-Options X-Content-Type-Options stops a browser from trying to MIME-sniff the content type and forces it to stick with the declared content-type. The only valid value for this header is “X-Content-Type-Options: nosniff”.
Issues here: http://www.dnsinspect.com/ews-o.com/1469628230
Wait for a reaction from an Avast Team Member to tell why your website comes or came flagged and mitigate mentioned insecurity.
He has been noticed by me.
polonus (volunteer website security analyst and website error-hunter)