v2.3.3 Vulnerability

Hi,

Two answers here.
1. Yes, we are reviewing the code to look at some edits to maintain functionality but not trigger this error as we know a number of users are concerned by the wordfence issue.
2. This version was created to comply with security issues raised by the WordPress Dev team and they concluded that this was safe for release. So, we need to make sure that any fix stays within their parameters for safety (ie. can’t just go back to the previous version that wordfence was fine with). That isn’t to say, however, that a user couldn’t use an older version if they felt more comfortable doing so.

Hope to have a further update regarding option (1) soon.

Any news here? Is the issue resolved?

I was wondering the same…