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.
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Link | Tags |
---|---|
http://www.securityfocus.com/bid/106220 | vdb entry third party advisory |
https://wordpress.org/support/wordpress-version/version-5-0-1/ | release notes vendor advisory |
https://codex.wordpress.org/Version_4.9.9 | product vendor advisory |
https://wpvulndb.com/vulnerabilities/9175 | vendor advisory |
https://github.com/WordPress/WordPress/commit/246a70bdbfac3bd45ff71c7941deef1bb206b19a | third party advisory patch |
https://www.debian.org/security/2019/dsa-4401 | third party advisory vendor advisory |
https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/ | release notes vendor advisory |
https://lists.debian.org/debian-lts-announce/2019/02/msg00019.html | third party advisory mailing list |
https://www.zdnet.com/article/wordpress-plugs-bug-that-led-to-google-indexing-some-user-passwords/ | press/media coverage third party advisory |