Viewing 5 replies - 1 through 5 (of 5 total)
  • I agree with that. You may contact patchstack to fix the report…

    Thread Starter danielspain

    (@danielspain)

    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.

    Thread Starter danielspain

    (@danielspain)

    Patchstack now shows that the issue is fixed in 1.9.12 but wp-toolkit stills reports the problem…

    Thread Starter danielspain

    (@danielspain)

    Now it’s resolved, wp-toolkit no longer reports the problems. Thanks to the plugin maintainer fo the fix!

    Plugin Support MaximeWPS

    (@seinomedia)

    Hello,

    Thanks for using WPS Hide Login.

    The issue has been fixed today and submitted to Patchstack.

    Their database will be updated today or tomorrow.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘vulnerability still reported by wp toolkit after upgrade to 1.9.12?’ is closed to new replies.