Security vulnerability not fixed through 2.1.4

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author totalsoft

    (@totalsoft)

    Hello, dear syzygist.

    Thank You. Now our team will try to solve your problem. Please wait for our reply.

    We are always happy to hear from you and solve all problems. We will develop the plugin with you. For us, the most important thing is that the plugin should be used by the developers themselves.

    Thank you very much.

    Plugin Author totalsoft

    (@totalsoft)

    Dear syzygist.

    I am glad to inform you that we have already fixed the issue in the latest version of the plugin and updated it accordingly.

    So, you can update the plugin to the latest version and check the case again.

    Waiting for your answer. Thank you in advance.

    Thread Starter syzygist

    (@syzygist)

    I restored the plugin files I had removed, updated to version 2.1.5, and ran a Wordfence scan. The scan did not flag the new version as vulnerable. However, the vulnerability report link I posted above has not been updated to mention the new version and identify it as a patch. You may wish to contact them about that.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Security vulnerability not fixed through 2.1.4’ is closed to new replies.