CVE-2017-9066 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9066): In WordPress before 4.7.5, there is insufficient redirect validation in the HTTP class, leading to SSRF. CVE-2017-9065 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9065): In WordPress before 4.7.5, there is a lack of capability checks for post meta data in the XML-RPC API. CVE-2017-9064 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9064): In WordPress before 4.7.5, a Cross Site Request Forgery (CSRF) vulnerability exists in the filesystem credentials dialog because a nonce is not required for updating credentials. CVE-2017-9063 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9063): In WordPress before 4.7.5, a cross-site scripting (XSS) vulnerability related to the Customizer exists, involving an invalid customization session. CVE-2017-9062 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9062): In WordPress before 4.7.5, there is improper handling of post meta data values in the XML-RPC API. CVE-2017-9061 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9061): In WordPress before 4.7.5, a cross-site scripting (XSS) vulnerability exists when attempting to upload very large files, because the error message does not properly restrict presentation of the filename.
The oldest version in the tree is 4.7.5 which, if I'm reading the reports correctly, is not vulnerable.
Thanks for the confirmation Anthony I'm closing the report since we have nothing else to do here. GLSA Vote: No