Hi there, @onjomax
There was a miscommunication by the Patchstack author. The issue is actually fixed in 2.4.1; but we had not specifically mentioned it in the readme. I guess they didn’t check the code. 🤭
Thread Starter
Peter
(@onjomax)
Hi @stephdau have you been able to hear back from patchstack?
Hi – Is there any sort of ETA on when this plugin will no longer be flagged by Wordfence? I am not able to finish up what I am working on until it’s no longer flagged. Thank you!
I contacted Patchstack last week about this to tell them it’s an error but I haven’t heard back from them yet. Once they update their site Wordfence will do too.
Thanks Sander! Glad that’s sorted out.
Donncha.
This is still showing up in the Wordfence scan as a security vulnerability.
Please help.
Thread Starter
Peter
(@onjomax)
@donncha Thank you all sorted from my side too.
Why was my first comment not approved? This plugin is still being flagged. Can someone fix that, please?
@emgb_520 your first comment was probably flagged because you left only a link. I’ve contacted Wordfence to ask them to remove that report. Just waiting on them to update their website.
Great – could you please update this thread when it’s been updated? Thank you!