WordPress before 5.1.1 does not properly filter comment content, leading to Remote Code Execution by unauthenticated users in a default configuration. This occurs because CSRF protection is mishandled, and because Search Engine Optimization of A elements is performed incorrectly, leading to XSS. The XSS results in administrative access, which allows arbitrary changes to .php files. This is related to wp-admin/includes/ajax-actions.php and wp-includes/comment.php.
References
Configurations
History
21 Nov 2024, 04:52
Type | Values Removed | Values Added |
---|---|---|
References | () http://www.securityfocus.com/bid/107411 - Third Party Advisory, VDB Entry | |
References | () https://blog.ripstech.com/2019/wordpress-csrf-to-rce/ - Exploit, Third Party Advisory | |
References | () https://github.com/WordPress/WordPress/commit/0292de60ec78c5a44956765189403654fe4d080b - Patch, Third Party Advisory | |
References | () https://lists.debian.org/debian-lts-announce/2019/03/msg00044.html - | |
References | () https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/ - Release Notes, Vendor Advisory | |
References | () https://wordpress.org/support/wordpress-version/version-5-1-1/ - Release Notes, Vendor Advisory | |
References | () https://wpvulndb.com/vulnerabilities/9230 - | |
References | () https://www.debian.org/security/2020/dsa-4677 - |
Information
Published : 2019-03-14 16:29
Updated : 2024-11-21 04:52
NVD link : CVE-2019-9787
Mitre link : CVE-2019-9787
CVE.ORG link : CVE-2019-9787
JSON object : View
Products Affected
wordpress
- wordpress
CWE
CWE-352
Cross-Site Request Forgery (CSRF)