Page 11 of 256 results (0.014 seconds)

CVSS: 6.4EPSS: 0%CPEs: 4EXPL: 0

In WordPress before 4.9.9 and 5.x before 5.0.1, when the Apache HTTP Server is used, authors could upload crafted files that bypass intended MIME type restrictions, leading to XSS, as demonstrated by a .jpg file without JPEG data. En WordPress, en versiones anteriores a la 4.9.9 y versiones 5.x anteriores a la 5.0.1, cuando se emplea el servidor HTTP de Apache, los autores podrían subir archivos arbitrarios que omiten las restricciones de tipo MIME planeadas, lo que conduce a Cross-Site Scripting (XSS). Esto queda demostrado por un archivo .jpg sin datos JPEG. • http://www.securityfocus.com/bid/106220 https://codex.wordpress.org/Version_4.9.9 https://github.com/WordPress/WordPress/commit/246a70bdbfac3bd45ff71c7941deef1bb206b19a https://lists.debian.org/debian-lts-announce/2019/02/msg00019.html https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release https://wordpress.org/support/wordpress-version/version-5-0-1 https://wpvulndb.com/vulnerabilities/9175 https://www.debian.org/security/2019/dsa-4401 https://www.zdnet.com/article/wordpress- • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 8.8EPSS: 0%CPEs: 1EXPL: 0

WordPress version 4.9.8 and earlier contains a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution due to an incomplete fix for CVE-2017-1000600. 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. WordPress en versiones 4.9.8 y anteriores 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. Esto se debe a una solución incompleta para CVE-2017-1000600. El ataque parece ser explotable mediante una miniatura subida por un usuario autenticado y podría requerir plugins adicionales para su explotación. • http://www.securityfocus.com/bid/105306 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: 8.8EPSS: 0%CPEs: 1EXPL: 0

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: 8.8EPSS: 45%CPEs: 3EXPL: 1

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: 0

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') •