mywebe1

Hello @kushnamdev ,

I am writing to second this issue reported by @viewgroup. I am also running this plugin and receiving security alerts (specifically from Kinsta’s system) regarding this vulnerability, which remains active because it is still marked as unresolved in the Patchstack database.

I understand you have implemented the fix, but until Patchstack updates its status, the automated scanners still flag our sites as vulnerable, which is causing ongoing administrative issues and concern.

Could you please provide an urgent update on your communication with Patchstack? It is crucial that the status is updated to ‘Resolved’ as quickly as possible.

Additionally, as a suggestion to speed up the process, could you please consider releasing a minor version update of the plugin? Changing the version number in the plugin’s main file is often the quickest way to force security tools and hosting scanners to re-run an automatic check on the code, which might resolve the visible alert even before Patchstack updates their entry manually.

Thank you for your attention to this. I appreciate the quick fix, but the removal of the alert is now the most critical priority.