It would have been more prudent, to public this vulnerability AFTER patch update (J! 3.1.6) is released - and not before.
It would have been more prudent, to public this vulnerability AFTER patch update (J! 3.1.6) is released - and not before.