An earlier version of this advisory incorrectly assumed that the only way to trigger this vulnerability was with routes containing ‘*action’. There are additional attack vectors and as a result all users are advised to upgrade to a fixed version as soon as possible.