See: https://urlscan.io/result/80128967-730d-4219-aee6-98b0cc9a97d4
Reputation Check
PASSED
Google Safe Browse: OK
Spamhaus Check: OK
Abuse CC: OK
Dshield Blocklist: OK
Cisco Talos Blacklist: OK
Web Server:
Apache
X-Powered-By:
PHP/7.2.21
IP Address:
198.54.125.177
Hosting Provider:
Namecheap.
Shared Hosting:
139 sites found on 198.54.125.177
Directory Indexing
In the test an attempt was made to list the directory contents of the uploads and plugins folders to determine if Directory Indexing is enabled. This is a common 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.
422 recommendations: https://webhint.io/scanner/d9ae17d2-7b93-46aa-ab1d-e218b237083f
polonus (volunteer 3rd party cold recon website security analyst and website error-hunter)
But one has to know when recommendations should be followed up and instances when this is not such a good idea.
For instance for Protocol Relative URLs: read -
https://technobabbl.es/2016/01/protocol-relative-urls-and-why-not-to-use-them/
This enabled the following abuse:
https://www.netresec.com/?page=Blog&month=2015-03&post=China's-Man-on-the-Side-Attack-on-GitHub
So configuration settings can be a two-sided-sword,with retire js found: for the chinese baidu script injections example->
jquery 3.2.1.min Found in -http://yingxiao.baidu.com/new/Public/static/Home/js/jquery-3.2.1.min.js?v=64c532e36e5403df70a70b7a01205c9e
Vulnerability info:
Medium CVE-2019-11358 jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution
WebGL invalid operations detected on fingerprint.js (pol),
see: https://www.cloudshark.org/captures/abfb3d44fa1c
We have been there before. see: https://forum.avast.com/index.php?topic=158336.0 
scan here: https://securityheaders.com/ With Apache this could go as far as: https://logging.apache.org/log4php/rat-report.html
polonus
There is a proposal now for websites with insecure outdated WP versions:
https://make.wordpress.org/core/2019/08/07/proposal-auto-update-old-versions-to-4-7/
This could lead to problems for users running certain plug-ins, certain insecure configurations, left code etc.
There is no cure for stupidity combined with sloppiness or when those that make decisions lack any relative knowledge
and still hold security for a last resort issue, where website maintanance is concerned.
WP websites make out 34,4 % of all websites online: https://w3techs.com/technologies/details/cm-wordpress/all/all
and some are quite big. Popular sites using WordPress
-Wordpress.com
-Otvfoco.com.br
-Chouftv.ma
-Exoclick.com
-Wordpress.org
-Geeksforgeeks.org
-Glassdoor.com
-Dkn.tv
-Okdiario.com
-Inquirer.net
polonus (volunteer 3rd party cold recon wesite security analyst and website error-hunter)
Another example, which is also a PHISH:
https://urlquery.net/report/f1bd3a32-dc0c-4bf2-9925-e00357450ac1
Re: https://www.virustotal.com/gui/url/fa89c41cdd9c5b73083b073e9ccdf27497b7ab135faf26650ca534dd02306736/detection
3 engines to detect;
Unknown upload status plug-in: sitepress-multilingual-cms
User Enumeration
The first two user ID’s were tested to determine if user enumeration is possible.
ID User Login
1 None AfsAdmin
2 None 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.
Directory Indexing
In the test an attempt was made to list the directory contents of the uploads and plugins folders to determine if Directory Indexing is enabled. This is a common 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.
156 recommendations upon linting: https://webhint.io/scanner/c5f0cd93-a2f8-426e-85d1-b08015e67037
query 1.12.4 Found in -https://afsgonulluleri.org/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
Vulnerability info:
Medium 2432 3rd party CORS request may execute CVE-2015-9251
Medium CVE-2015-9251 11974 parseHTML() executes scripts in event handlers
Medium CVE-2019-11358 jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, …) because of Object.prototype pollution
polonus (volunteer 3rd party cold recon website security analyst and website error-hunter)
Malicious on outdated WordPress version: https://urlquery.net/report/8f2cc5a0-8306-4e7a-8148-65e6ddc533ad
Re: https://urlhaus.abuse.ch/url/182714/
Detected by avast? → https://www.virustotal.com/gui/file/18bbd30411778c812f8261c8301b1ef6dae3a3a0c004c597ef3188bb4562ead2/detection
-http://arenaaydin.com is in Dr.Web malicious sites list!
User Enumeration
The first two user ID’s were tested to determine if user enumeration is possible.
ID User Login
1 None arenaaydin
2 None 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.
Directory Indexing
In the test an attempt was made to list the directory contents of the uploads and plugins folders to determine if Directory Indexing is enabled. This is a common 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.
polonus
The following webpage has outdated Word Press software and does not comply with EU cookie law:
https://www.cookiemetrix.com/display-report/medicoversenior.pl/a466bc686d91403a0008b0ceb7094ae2
https://urlquery.net/report/c51cdd97-8569-4830-aea5-06fe0a76ad9b
DOM-XSS issues: Results from scanning URL: -https://medicoversenior.pl/wp-content/plugins/responsive-lightbox/js/front.js?ver=2.1.0
Number of sources found: 41
Number of sinks found: 17
bootstrap 3.1.1 Found in -https://medicoversenior.pl/wp-content/themes/startuply-clean/js/lib/bootstrap.min.js?ver=5.2.2
Vulnerability info:
High 28236 XSS in data-template, data-content and data-title properties of tooltip/popover CVE-2019-8331
Medium 20184 XSS in data-target property of scrollspy CVE-2018-14041
Medium 20184 XSS in collapse data-parent attribute CVE-2018-14040
Medium 20184 XSS in data-container property of tooltip CVE-2018-14042
jquery 1.12.4 Found in -https://medicoversenior.pl/wp-includes/js/jquery/jquery.js?ver=1.12.4-wp
Vulnerability info:
Medium 2432 3rd party CORS request may execute CVE-2015-9251
Medium CVE-2015-9251 11974 parseHTML() executes scripts in event handlers
Medium CVE-2019-11358 jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, …) because of Object.prototype pollution 123
jquery 1.4.2 Found in -https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
Vulnerability info:
Medium CVE-2011-4969 XSS with location.hash
Medium CVE-2012-6708 11290 Selector interpreted as HTML
Medium 2432 3rd party CORS request may execute CVE-2015-9251
Medium CVE-2019-11358 jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, …) because of Object.prototype pollution
618 linting recommendations: https://webhint.io/scanner/f99c6e20-25b0-4518-91d7-ff8d64fc107f
polonus (volunteer 3rd party cold recon website security analyst and website error-hunter)
Has this threat been taken down? → https://urlquery.net/report/3e2a0ba3-b970-4fa1-8f1d-75bd58b97dbc
F-grade status: https://observatory.mozilla.org/analyze/centurystage.com
no content returned here: https://aw-snap.info/file-viewer/?protocol=secure&ref_sel=GSP2&ua_sel=ff&chk-cache=&fs=1&tgt=d3d3Ll57bnR1fXlzdHxney5eXW0%3D~enc
IP found in database: https://www.abuseipdb.com/check/103.247.141.199
web app and brute-force-attacks;
Detection: https://urlhaus.abuse.ch/host/centurystage.com/
It’s possible that the malware payload is offline or requests are being blocked…
Abuse: Reputation Check
PASSED
Google Safe Browse: OK
Spamhaus Check: OK
Abuse CC: OK
Dshield Blocklist: OK
Cisco Talos Blacklist: OK
Web Server:
nginx
X-Powered-By:
PHP/5.6.40
IP Address:
103.247.141.199
Hosting Provider:
WTT HK Limited
Shared Hosting:
124 sites found on 103.247.141.199
See: https://www.immuniweb.com/websec/?id=1zFODux1 - > mnemonic_dns blacklisted
Privacy Policy was not found on the website or is not easily accessible.
Misconfiguration or weakness
polonus
But WordPress is even used on bulletproof hosters of questionable nature:
Read on AS: https://krebsonsecurity.com/tag/hostsailor-com/
Full of malicious hosts and reported by cybercrime tracker:
PORT STATE SERVICE VERSION
80/tcp open http Apache httpd 2.2.15 ((CentOS))
| http-methods:
|_ Potentially risky methods: TRACE
|_http-server-header: Apache/2.2.15 (CentOS)
|_http-title: Apache HTTP Server Test Page powered by CentOS
-> https://toolbar.netcraft.com/site_report?url=dedi46647.hostsailor.com
-> https://www.shodan.io/host/185.183.96.100
On SPI tunneling of bulletproof dedicated hosting:
https://www.tunnelsup.com/learning-about-asp-tables-spi-and-vpn-contexts/
but exploitable: https://www.exploit-db.com/exploits/36663 & https://www.exploit-db.com/exploits/45001
→ https://www.shodan.io/host/185.82.203.174
Consider: https://toolbar.netcraft.com/site_report?url=dedi46647.hostsailor.com
and https://www.virustotal.com/gui/ip-address/104.20.109.70/details
Abuse all sorts: https://www.abuseipdb.com/check/185.82.203.174
Further relations: https://censys.io/domain?q=dedi46647.hostsailor.com+
TLS recommendations etc,: https://sitecheck.sucuri.net/results/https/hostsailor.com
See: https://aw-snap.info/file-viewer/?protocol=secure&ref_sel=GSP2&ua_sel=ff&chk-cache=&fs=1&tgt=aF1zdHN8W2xdfS5eXW0%3D~enc
Google Chrome returned code 0
GoogleBot returned code 0
polonus (volunteer 3rd party cold recon website security analyst & website error-hunter)