CVSS: 8.8EPSS: 1%CPEs: 1EXPL: 0CVE-2017-1000600 – WordPress Core < 4.9 - Insecure Deserialization
https://notcve.org/view.php?id=CVE-2017-1000600
WordPress version <4.9 contains a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution. This attack appears to be exploitable via thumbnail upload by an authenticated user and may require additional plugins in order to be exploited however this has not been confirmed at this time. This issue appears to have been partially, but not completely fixed in WordPress 4.9 WordPress en versiones anteriores a la 4.9 contiene una vulnerabilidad de validación de entradas (CWE-20) en el procesamiento de miniaturas que puede resultar en la ejecución remota de código. El ataque parece ser explotable mediante una miniatura subida por un usuario autenticado y podría requerir plugins adicionales para su explotación. Sin embargo, esto aún no ha sido confirmado. • http://www.securityfocus.com/bid/105305 https://www.theregister.co.uk/2018/08/20/php_unserialisation_wordpress_vuln https://youtu.be/GePBmsNJw6Y?t=1763 • CWE-20: Improper Input Validation CWE-502: Deserialization of Untrusted Data •
CVSS: 7.2EPSS: 19%CPEs: 1EXPL: 0CVE-2018-14028 – WordPress Core < 6.4.3 - Authenticated(Administrator+) PHP File Upload
https://notcve.org/view.php?id=CVE-2018-14028
In WordPress 4.9.7, plugins uploaded via the admin area are not verified as being ZIP files. This allows for PHP files to be uploaded. Once a PHP file is uploaded, the plugin extraction fails, but the PHP file remains in a predictable wp-content/uploads location, allowing for an attacker to then execute the file. This represents a security risk in limited scenarios where an attacker (who does have the required capabilities for plugin uploads) cannot simply place arbitrary PHP code into a valid plugin ZIP file and upload that plugin, because a machine's wp-content/plugins directory permissions were set up to block all new plugins. En WordPress 4.9.7, los plugins subidos mediante el área de admin no se verifican como archivos ZIP. • http://www.securityfocus.com/bid/105060 https://core.trac.wordpress.org/ticket/44710 https://github.com/rastating/wordpress-exploit-framework/pull/52 https://rastating.github.io/unrestricted-file-upload-via-plugin-uploader-in-wordpress • CWE-434: Unrestricted Upload of File with Dangerous Type •
CVSS: 8.8EPSS: 45%CPEs: 3EXPL: 1CVE-2018-12895 – WordPress Core < 4.9.7 - Authenticated Arbitrary File Deletion
https://notcve.org/view.php?id=CVE-2018-12895
WordPress through 4.9.6 allows Author users to execute arbitrary code by leveraging directory traversal in the wp-admin/post.php thumb parameter, which is passed to the PHP unlink function and can delete the wp-config.php file. This is related to missing filename validation in the wp-includes/post.php wp_delete_attachment function. The attacker must have capabilities for files and posts that are normally available only to the Author, Editor, and Administrator roles. The attack methodology is to delete wp-config.php and then launch a new installation process to increase the attacker's privileges. WordPress hasta la versión 4.9.6 permite que los usuarios Author ejecuten código arbitrario aprovechándose de un salto de directorio en el parámetro thumb en wp-admin/post.php que se pasa a la función unlink en PHP y puede borrar el archivo wp-config.php. • http://packetstormsecurity.com/files/164633/WordPress-4.9.6-Arbitrary-File-Deletion.html http://www.securityfocus.com/bid/104569 https://blog.ripstech.com/2018/wordpress-file-delete-to-code-execution https://lists.debian.org/debian-lts-announce/2018/07/msg00046.html https://wpvulndb.com/vulnerabilities/9100 https://www.debian.org/security/2018/dsa-4250 • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •
CVSS: 6.1EPSS: 0%CPEs: 3EXPL: 0CVE-2018-10100 – WordPress Core < 4.9.5 - Open Redirect
https://notcve.org/view.php?id=CVE-2018-10100
Before WordPress 4.9.5, the redirection URL for the login page was not validated or sanitized if forced to use HTTPS. En versiones anteriores a la 4.9.5 de WordPress, la URL de redirección para la página de inicio de sesión no se validó o saneó si se forzó el uso de HTTPS. • http://www.securitytracker.com/id/1040836 https://codex.wordpress.org/Version_4.9.5 https://core.trac.wordpress.org/changeset/42892 https://github.com/WordPress/WordPress/commit/14bc2c0a6fde0da04b47130707e01df850eedc7e https://lists.debian.org/debian-lts-announce/2018/04/msg00031.html https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release https://wpvulndb.com/vulnerabilities/9054 https://www.debian.org/security/2018/dsa-4193 • CWE-601: URL Redirection to Untrusted Site ('Open Redirect') •
CVSS: 6.1EPSS: 0%CPEs: 3EXPL: 0CVE-2018-10101 – WordPress Core < 4.9.5 - Security Misconfiguration with URL Hostnames
https://notcve.org/view.php?id=CVE-2018-10101
Before WordPress 4.9.5, the URL validator assumed URLs with the hostname localhost were on the same host as the WordPress server. En versiones anteriores a la 4.9.5 de WordPress, el validador de URL asumía URL con el nombre de host del localhost en el mismo host que el servidor de WordPress. • http://www.securityfocus.com/bid/104350 http://www.securitytracker.com/id/1040836 https://codex.wordpress.org/Version_4.9.5 https://core.trac.wordpress.org/changeset/42894 https://github.com/WordPress/WordPress/commit/804363859602d4050d9a38a21f5a65d9aec18216 https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release https://wpvulndb.com/vulnerabilities/9053 https://www.debian.org/security/2018/dsa-4193 • CWE-601: URL Redirection to Untrusted Site ('Open Redirect') •