Since WP is providing security patches back to WP4.7, I assume this vulnerability affects ClassicPress?
tagging @timkaye here but I would strongly advise to sensibly report such concerns in private to the core team next time. I think today during the core team meeting those concerns can be raised too.
We’ll be releasing a security update very soon, just as we did after the other recent WP security updates.
Version 2.7.3 has now been released and addresses this issue (among others).