Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
That’s not really a WordPress issue, more like a patch in WordPress would address a host configuration problem with the web server.
See the remediation section here.
http://blog.dewhurstsecurity.com/2017/05/04/exploitbox-wordpress-security-advisories.html
Which really goes here for a httpd.conf option.
https://httpd.apache.org/docs/2.4/mod/core.html#usecanonicalname
Mind you, on my nginx web server this isn’t a problem.
-
This reply was modified 8 years, 12 months ago by
Jan Dembowski. Reason: Fixing silly typo
There are two parts to that remediation section, the first offers a server solution to use the canonical name, but the second is WP could use home or siteurl instead of SERVER_NAME to solve it for every install regardless of server flavour.
If looking up the SERVER_NAME/host is the vulnerability in both instances wouldn’t it make sense to instead use the configured value, or is there some benefit at the WP end to using SERVER_NAME in wp-includes/pluggable.php?
There is a public ticket about this issue which you can follow here:
https://core.trac.ww.wp.xz.cn/ticket/25239