• Resolved kevinbrands

    (@kevinbrands)


    Our maintenance tool tells us there is a vulnerability in version 1.4.0. Are you aware of this? And will there be an update soon?

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • My client is getting the same warning from iThemes security.

    iThemes explanation.

    Plugin Author tychesoftwares

    (@tychesoftwares)

    Hi All,

    I sincerely apologize for this inconvenience & thank you for bringing this to our attention. We take security vulnerabilities very seriously and we are currently investigating the issue. We will provide an update as soon as possible.

    Thank you again for your help and for your patience.

    @tychesoftwares, thanks very much for the quick response. Looking forward to the update.

    Plugin Author tychesoftwares

    (@tychesoftwares)

    Hi All,

    We are pleased to inform you that we have released an updated version 1.4.1 of our plugin that addresses the previously reported issue. The new version is now available for download in the plugins section of your account.

    We strongly recommend that you update your plugin to the latest version as soon as possible. If you need any assistance, please do not hesitate to contact us.

    Thank you for your patience.

    @tychesoftwares, just performed a full backup and updated the Custom Order Numbers for WooCommerce plugin. Placed a test order and everything seems to be working normally.

    Thank you very much for the prompt response, it’s truly appreciated and keep up the great work!

    Hi @tychesoftwares, thanks for this revised version. After upgrading to the latest version 1.4.1, the plugin asked me to update database. Then I got an admin message: “Database updated successfully. In addition to new orders henceforth, you can now also search the old orders on Orders page with the custom order numbers”.

    This message is always there, even I clicked the Dismiss (x) icon. Would you please confirm this issue and let me know how to fix it? Thank you.

    Plugin Author tychesoftwares

    (@tychesoftwares)

    Hi @3y5hx9cxwkvam5h5,

    We have not added this message in this release. Could you deactivate the plugin once and then reactivate it and check?

    And you can create new post for this new issue.

    Hi @tychesoftwares. Okay, I will create a new post for this, thank you.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Vulnerability in 1.4.0’ is closed to new replies.