WhatWeb identifies websites. Its goal is to answer the question, “What is that Website?”. WhatWeb recognises web technologies including content management systems (CMS), blogging platforms, statistic/analytics packages, JavaScript libraries, web servers, and embedded devices. WhatWeb has over 900 plugins, each to recognise something different. WhatWeb also identifies version numbers, email addresses, account IDs, web framework modules, SQL errors, and more.

WhatWeb can be stealthy and fast, or thorough but slow. WhatWeb supports an aggression level to control the trade off between speed and reliability. When you visit a website in your browser, the transaction includes many hints of what web technologies are powering that website. Sometimes a single webpage visit contains enough information to identify a website but when it does not, WhatWeb can interrogate the website further. The default level of aggression, called ‘passive’, is the fastest and requires only one HTTP request of a website. This is suitable for scanning public websites. More aggressive modes were developed for in penetration tests.

Most WhatWeb plugins are thorough and recognise a range of cues from subtle to obvious. For example, most WordPress websites can be identified by the meta HTML tag, e.g. ‘‘, but a minority of WordPress websites remove this identifying tag but this does not thwart WhatWeb. The WordPress WhatWeb plugin has over 15 tests, which include checking the favicon, default installation files, login pages, and checking for “/wp-content/” within relative links.

* Over 900 plugins

* Control the trade off between speed/stealth and reliability

* Plugins include example URLs

* Performance tuning. Control how many websites to scan concurrently.

* Multiple log formats: Brief (greppable), Verbose (human readable), XML, JSON, MagicTree, RubyObject, MongoDB.

* Recursive web spidering

* Proxy support including TOR

* Custom HTTP headers

* Basic HTTP authentication

* Control over webpage redirection

* Nmap-style IP ranges

* Fuzzy matching

* Result certainty awareness

* Custom plugins defined on the command line

Using WhatWeb on a couple of websites:

El uso masivo de CMS hace que los criminales se centren en este tipo de aplicativos para buscar vulnerabilidades. Además los exploits en los que el atacante consigue subir algún tipo de archivo al servidor remoto, los usan para infectarlos y por ejemplo poner Exploits Kits con los que los usuarios que acceden al site web quedan infectados.

Las medidas para que no ocurran estas cosas ya las conocemos, actualizar siempre el core de la aplicación, y sobretodo los plugins de terceros que se sabe que no se revisa en la parte de seguridad igual que el core de la aplicación.

Además de todo esto, en WordPress tenemos plugins que nos ayudarán a mejorar un poco mas la seguridad del CMS . En este caso tenemos WP-WAF. Este plugin lo podemos encontrar en el repositorio de plugins de WordPress y para instalarlo solo hace falta que lo copiemos a la carpeta plugins dentro de wp-content.

La configuración del plugin es muy sencilla.