Hi again Mark,
In the latest version of Wordfence (5.1.4) this bug appears to have returned.
Can you have a look and perhaps fix it again if poss.
To be honest, it's not so much of a problem now that you have implemented your other excellent security features in recent updates, but I feel that I should bring it to your attention.
Cheers, Paul