Author Topic: Outdated CMS, 73 security errors, malware detected on website.  (Read 2103 times)

0 Members and 1 Guest are viewing this topic.

Offline polonus

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 34051
  • malware fighter
Re 73 errors: PERMALINK

https://sonarwhal.com/scanner/6a4e1a9c-8a8e-4c8b-a939-acd7a2ed5e95

Update now, for WordPress Version 4.8.7
Version does not appear to be latest

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

onesignal-free-web-push-notifications 1.14.3   latest release (1.16.7) Update required
https://onesignal.com/
yuzo-related-post 5.12.69   latest release (5.12.78) Update required
https://wordpress.org/plugins/yuzo-related-post/
wp-social-widget 2.0.2   latest release (2.1.2) Update required
https://wordpress.org/plugins/wp-social-widget/
w3-total-cache 0.9.5.4   latest release (0.9.7) Update required
https://www.w3-edge.com/wordpress-plugins/w3-total-cache/
wordpress-seo 3.5   latest release (7.9) Update required
https://yoa.st/1uj
easy-modal 2.1.0   latest release (2.1.0)
http://easy-modal.com
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.
Quote
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   ricardofcorreia
2   None   andredias
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.
Fortinet's flags: https://urlquery.net/report/3ca0b317-c48e-4c0f-809a-8451c66fb59f

suspicious: maxruntime exceeded 10 seconds
wXw.maiscursos.org/wp-content/plugins/easy-modal/assets/scripts/jquery.transit.min.js?ver=0.9.11
script error
Quote
-www.maiscursos.org/wp-includes/js/wp-embed.min.js?ver=4.8.7
     info: [decodingLevel=0] found JavaScript
     error: line:72: SyntaxError: invalid label:
          error: line:72: ;{"@context":"http:\/\/schema.org","@type":"WebSite","@id":"#website","url":"http:\/\/-www.maiscursos.org\/","name":"Mais Cursos","alternateName":"Cursos Profissionais","potentialAction":{"@type":"SearchAction","target":"http:\/\/-www.maiscursos.org\/?s={se
          error: line:72: ..^
     error: line:3: SyntaxError: missing = in XML attribute:
          error: line:3: <!DOCTYPE html>
          error: line:3: ..............^
     file: 8531fd5981d26d7a6c3b7ff85c3e8382840a84c5: 99866 bytes

polonus (volunteer 3rd party cold reconnaissance website security analyst and website error-hunter)
Cybersecurity is more of an attitude than anything else. Avast Evangelists.

Use NoScript, a limited user account and a virtual machine and be safe(r)!

Offline polonus

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 34051
  • malware fighter
Re: Outdated CMS, 73 security errors, malware detected on website.
« Reply #1 on: August 06, 2018, 03:25:39 PM »
Some additional comments on this 3rd party scan of above insecure website.

suggest.js could or rather should be alterted/removed because of
https://www.jqueryscript.net/demo/Simple-Inline-Autocomplete-Autosuggest-Plugin-suggest-js/
uBlock blocks as found in Dan Pollock's host file.

It is not found in aw snap scan results here: https://aw-snap.info/file-viewer/?protocol=not-secure&tgt=www.maiscursos.org&ref_sel=GSP2&ua_sel=ff&fs=1
So it is a non-public interior file.  ;), but still 3rd party cold reconnaissance scannable.

This should be removed and is still there: zxcvbn-async.min.js wordpress

Deadlinks we have found:
Quote

##/.png
K##/comments/
##/fonts.googleapis.com/
##/s.w.org/
##/OneSignalSDKUpdaterWorker.js.php
##/OneSignalSDKWorker.js.php
##/wp-includes/wlwmanifest.xml/
K##/fonts.googleapis.com
##/s.w.org

And again we find why PHP is a bitch: https://stackoverflow.com/questions/45769522/disable-zxcvbn-min-js-in-wordpress-and-woocommerce 
Handle PHP in PHP-based CMS  only with some solid cheatsheets next to it,
to evade most of the common security traps.

Nothing is fully secure in this here world of ours,
but old polonus here at the other side of your screen likes to do the security scan job as best he can,
and he's learning all of the time all the time  :D .

polonus aka Damian

P.S. Also blocked by my ad-blocker as ad-tracker server: htxps://cdn.onesignal.com/sdks/OneSignalSDK.js

D
« Last Edit: August 06, 2018, 04:13:57 PM by polonus »
Cybersecurity is more of an attitude than anything else. Avast Evangelists.

Use NoScript, a limited user account and a virtual machine and be safe(r)!