Blocked

That CVE description (I have no idea who submitted it) isn’t even right – apparently they didn’t even take enough time to read the changelog entry that they based it on accurately. As the changelog entry says, the vulnerability was not open to arbitrary remote attackers, but required individual targeting of a known logged in user and requiring them to visit a personally crafted link.

But, to answer the question, I have no idea. You’re asking what criteria your hosting company is using to ban the plugin. Only your hosting company can tell you that. The best thing to do would be to ask them.