Source: wordpress Version: 4.9.8 Severity: normal Tags: security upstream
WordPress 5.0.1 has been released upstream which addresses multiple security issues[1] * Karim El Ouerghemmi discovered that authors could alter meta data to delete files that they weren’t authorized to. * Simon Scannell of RIPS Technologies discovered that authors could create posts of unauthorized post types with specially crafted input. * Sam Thomas discovered that contributors could craft meta data in a way that resulted in PHP object injection. * Tim Coen discovered that contributors could edit new comments from higher-privileged users, potentially leading to a cross-site scripting vulnerability. * Tim Coen also discovered that specially crafted URL inputs could lead to a cross-site scripting vulnerability in some circumstances. WordPress itself was not affected, but plugins could be in some situations. * Team Yoast discovered that the user activation screen could be indexed by search engines in some uncommon configurations, leading to exposure of email addresses, and in some rare cases, default generated passwords. * Tim Coen and Slavco discovered that authors on Apache-hosted sites could upload specifically crafted files that bypass MIME verification, leading to a cross-site scripting vulnerability. Phew! Given it goes back to 3.8, it impacts every dist back to old stable. I'll raise some CVE requests if they are not already in train. 1: https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/ -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
