• Resolved bramvds

    (@bramvds)


    Hi,

    My site got hacked through post smtp version 2.8.6.

    They entered the email log and used the password reset link.

    Now i was told by my host, cloudways, not to use this plugin anymore.

    But i really like it, so to be sure, was it because of version 2.8.6 or is this still a problem?

    Thanks

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Author Saad Iqbal

    (@saadiqbal)

    Hi @bramvds,

    Hope you are doing good. As @patrick1994 mentioned, this issue was fixed in 2.8.8. Our fix has been verified by Wordfence team so you can confidently continue to use it.

    Sorry for the inconvenience. We’ll keep double check in our upcoming releases to avoid any such issues in future.

    Still do let us know if there is any thing else we can help you with.

    Thanks

    lol all site hacked…

    Nasty – for anyone else who arrives here; hardening of wp-content directory helps to prevent web user from having write access. Restore from backup – and confirm no files have been changed. Install further 2FA plugin and deny access to any wp-admin areas by use of IP based Cloudflare WAF rule or similar. We use this module to hook into SendGrid – have kept with it – but kept logging off – as they appear in SendGrid regardless.

    • This reply was modified 10 months, 1 week ago by newaytech.

    @newaytech me too. We have now fixed it but this caused a disaster on about 360 sites. A disaster, I will definitely uninstall this plugin as soon as possible. A fatal error!

    My website was also hacked because of the security hole in the plugin. Uninstaling and never looking back.

    This plugin deserves to fall into irrelevance after this recent dumpster fire .. do you guys have no QA ???!!!

    Wheres the PR ?

    @dilusionz The problem is that these are basic flaws, plus this plugin saves sensitive data of some users in the various logs. On top of that it is offered premium for a fee, I would like to ask the dev in these cases if they are the ones who fix the problem on all sites due to a fault on their part, or is it always to the detriment of those who use it.

    Plugin Author Saad Iqbal

    (@saadiqbal)

    Hi?@minimamente @manouallou?@dilusionz,

    I sincerely apologize for the challenges you’ve experienced with our plugin, and I understand the frustration this situation has caused for you and other WordPress developers. I want to assure you that we take this matter very seriously, and we are actively working to help our users.

    To provide some context, we are working in collaboration with renowned security research teams such as Wordfence and Patchstack WordPress Security. This partnership allows us to stay ahead of potential security vulnerabilities, and together we continuously research and address any issues that may arise.

    Regarding the lack of communication and notifications, I acknowledge that we fell short in keeping you informed, and for that, I’m truly sorry. We are taking steps to improve our communication channels to ensure that such incidents are promptly and clearly communicated to our user community in the future.

    To address the recent security vulnerability:

    We had released an urgent update (V2.8.8 – 2024-01-01) that includes a fix for the identified issue.
    Moving forward, we are implementing additional measures to enhance the security of our plugin to prevent similar occurrences.

    I understand the impact this has had on your workload, and I genuinely regret any inconvenience caused.

    If you have any further questions or if there’s anything else we can do to assist you, please don’t hesitate to reach out. We value your feedback, and your experience is important to us.

    Best regards,
    Saad Iqbal

    @saadiqbal not just excuses. The damage is huge for web agencies that use your plugins. BUT how can you not put a basic sanitize?

    Hi @saadiqbal and thank you for your response, although a bit late since my website has been already hacked.

    I know I shouldn’t be asking a lot from a free plugin BUT security should be a no.1 concern for developers especially If they also offer a premium version.

    Anyhoo, the damage is done now and this is a lesson for me. Always backup your website and be ready for disaster recovery.

    Yesterday was your plugin that caused trouble, tomorrow may be another.

    One thing for sure though. If I had paid for your premium plugin, I would have gone after you legally. On the free side of things, I shut up, create a disaster mitigation plan and go on with my life. Without your plugin in my, or my clients’ sites.

    I hope that your collaboration with security experts will serve you well in the future.

    All the best,

    Manou

    @manouallou I completely agree! This involves not only the time to restore but also the time to secure.

    See here: https://cloudup.com/cb06yKtDFDP

    • This reply was modified 10 months, 1 week ago by minimamente.
    Plugin Author Saad Iqbal

    (@saadiqbal)

    @minimamente We take full responsibility for our mistake and are committed to improving our plugin quality and security.

    @manouallou We are always making extra efforts to resolve and improve things in our plugin, regardless of whether it is a free or pro version.

    This is the first time we have experienced such a high level of vulnerability penetration, and we are determined to ensure it never happens again.

    Best regards,
    Saad Iqbal

    Same here, also had two websites affected.

    I was able to restore my database and files. If you can’t, for some reason, at least check if the attackers created an “app password” for your admin user and remove that after changing passwords and disconnecting sessions. Turning off app passwords is also recommended.

    pratt2

    (@pratt2)

    can anyone tell how far back the GET query pulls the logs? I can’t tell if the pull gives you 25 or all 250 last items of the log.

    I can see a generic query to get-logs then I see multiple queries to specific id’s (I assume to see the full log entry for that one email)

    I am basically trying to figure out if all 250 items in the log were queried versus a subset

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘site hacked through post smtp 2.8.6 email log’ is closed to new replies.