Parked Word Press site now vulnerable through PHP insecurity?

Viruses and worms
1

L.S.

See: https://urlscan.io/result/9abe29c4-1625-42ec-b105-987748d33682/
Re 15 security hints: https://webhint.io/scanner/dea97788-c2e1-4c54-b3ad-8fa7befa4eab#Security
No alerts here: https://urlquery.net/report/01af25c3-5230-4627-965b-6662506bd5b2
See: https://aw-snap.info/file-viewer/?protocol=not-secure&ref_sel=GSP2&ua_sel=ff&chk-cache=&fs=1&tgt=Yn17fGtmLl5dbQ%3D%3D~enc
IP found in their database: https://www.abuseipdb.com/check/194.9.94.85
Malware, PHISHING, botnet and malware activities reported: https://cymon.io/194.9.94.85
Most users voted this as malicious: https://www.threatcrowd.org/ip.php?ip=194.9.94.85
Server: -194.9.95.59
nginx/1.12.2 ASN: 39570 Sweden
Loopia AB Reverse DNS:
-controlcluster.loopia.com Outdated PHP/5.6.36-> https://sitecheck.sucuri.net/results/https/www.loopia.com/wordpress/
See: https://aw-snap.info/file-viewer/?protocol=secure&ref_sel=GSP2&ua_sel=ff&chk-cache=&fs=1&tgt=d3d3LmxdXXBbfC5eXW1g~enc (form-elements without labels!).

polonus (volunteer website security analyst and website error-hunter)

2

Here on a non-parked site we can see what such vulnerability can lead to e.g. site became fortinet’s malware blacklisted:

https://urlquery.net/report/ecb5fc24-73a5-4ab6-9aa3-31099132155c

WordPress Version
4.8.5
Version does not appear to be latest 4.9.8 - update now.

WordPress Plugins
The following plugins were detected by reading the HTML source of the WordPress sites front page.

wordpress-seo 5.6.1 latest release (9.2.1) Update required
https://yoa.st/1uj
tablepress 1.8 latest release (1.9.1) Update required
https://tablepress.org/
tabs-responsive 1.7.7 latest release (1.8.8) Update required
https://www.wpshopmart.com/plugins
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.

Outdated Word Press and PHP detected: https://sitecheck.sucuri.net/results/klebedbelagavi.org
Consider also: https://aw-snap.info/file-viewer/?protocol=not-secure&ref_sel=GSP2&ua_sel=ff&chk-cache=&fs=1&tgt=a2x7YnsjYntsfGd8dlsuXX1nYA%3D%3D~enc

3 vulnerable jQuery libraries found: https://retire.insecurity.today/#!/scan/41190d5109589b4a5a9ac6e23f7cdb14644ec0940169e68a8b981809d5f83b19

57 security recommendations: https://webhint.io/scanner/9d421d6e-183f-4caa-a400-c3f632a81593#Security

polonus (volunteer 3rd party cold reconnaissance website security analyst and website error-hunter)

3

On JQuery function errors here:

JavaScript errors because of XSS in data-target attribute function goes back a long time with JavaScript lacking HTML creating some basic hick-ups. This weakness originated from the time a century ago when JavaScript was left loose unto the Interwebs prematurely, as it was not ready i.m.h.o. What we discuss below follows from these earlier manco’s.

Read: https://github.com/twbs/bootstrap/issues/20184 (see retirable jQuery libraries mentioned in previous post,
and further discussed here: https://stackoverflow.com/questions/18602331/why-is-this-jquery-click-function-not-working.

Needs a bit of understanding of JavaScript errors to appreciate above developer discussions at StackOverflow. However we expect solutions to come at the other side of a new version of that particular library. Info credits here go to Reid Mirre - for bootstrap at Github’s

polonus (volunteer website security-analyst and website error-hunter)