I agree with that. You may contact patchstack to fix the report…
Hello, perhaps the best thing to do is to have the maintainer of the plugin do it to report the correction correctly. What I don’t know is how to make wp-toolkit aware of the patch and version that is not affected (the current one) and not report it, because otherwise it will continue to mark the problem. I upgraded the plugin and rescanned the site with wp-toolkit and it keeps reporting it as unfixed even though it says it affects the previous version 1.9.11. It will be an ongoing problem if not’s fixed by wp-toolkit.
Patchstack now shows that the issue is fixed in 1.9.12 but wp-toolkit stills reports the problem…
Now it’s resolved, wp-toolkit no longer reports the problems. Thanks to the plugin maintainer fo the fix!