A: Hey there,

This was nothing but an irresponsible action by WordPress. There was no vulnerability in the latest version, the issue was in the previous version at that time. They didn't verify the problem properly and took our plugin down for a few days. However they fixed it as soon as they realized the mistake.