From the WordPress 4.8.2 release post: WordPress versions 4.8.1 and earlier are affected by nine security issues:
$wpdb->prepare()can create unexpected and unsafe queries leading to potential SQL injection (SQLi). WordPress core is not directly vulnerable to this issue, but we’ve added hardening to prevent plugins and themes from accidentally causing a vulnerability. Reported by Slavco.
- A cross-site scripting (XSS) vulnerability was discovered in the oEmbed discovery. Reported by xknown of the WordPress Security Team.
- A cross-site scripting (XSS) vulnerability was discovered in the visual editor. Reported by Rodolfo Assis (@brutelogic) of Sucuri Security.
- A path traversal vulnerability was discovered in the file unzipping code. Reported by Alex Chapman (noxrnet).
- A cross-site scripting (XSS) vulnerability was discovered in the plugin editor. Reported by 陈瑞琦 (Chen Ruiqi).
- An open redirect was discovered on the user and term edit screens. Reported by Yasin Soliman (ysx).
- A path traversal vulnerability was discovered in the customizer. Reported by Weston Ruter of the WordPress Security Team.
- A cross-site scripting (XSS) vulnerability was discovered in template names. Reported by Luka (sikic).
- A cross-site scripting (XSS) vulnerability was discovered in the link modal. Reported by Anas Roubi (qasuar).
In addition to the security issues above, WordPress 4.8.2 contains six maintenance fixes to the 4.8 release series.
- #41794 – Support numbers in locales during installation
- #13377 – Add more sanitization in _cleanup_header_comment
- #41596 – New Text Widget recognizes HTML but does not render it in the front end
- #41622 – Text widget can show DOMDocument::loadHTML() warnings in admin when is_legacy_widget method is called
List of Files Revised