As a result, forty-three million records were stolen, including customer names, email addresses, and IP addresses.
However, LeakedSource, a reliable hacking news source, spoke of their relief when it came to reaching out to the Weebly team about their data breach:
“Unlike nearly every other hack, the Co-founder and CTO of Weebly Chris Fanini fortunately did not have his head burried deeply in the sand and actually responded to our communication requests. We have been working with them to ensure the security of their users meaning password resets as well as notification emails are now being sent out.
This mega breach affects not only tens of millions of users but tens of millions of websites and with Weebly being one of the most popular hosting platforms in the world, this breach could have been far more disastrous in the wrong hands had they not strongly hashed passwords.”
So, kudos to Weebly for cooperating with the LeakedSource team (instead of shunning them, like Twitter once did), and also for safeguarding passwords with a relatively high level of encryption.
Customer Payment Information Remains Secure
Thankfully, Weebly also confirmed in an email to customers that they don’t believe any of their hosted websites were improperly accessed. They also made it clear that they don’t store credit card information, so their customers are safe on that front.
LeakedSource also claimed that password resets were being issued by Weebly – but if you’re a Weebly user and you haven’t changed your password since February, I strongly suggest changing it right away.
To follow this news as it develops, LeakedSource’s official Twitter page seems to be the place to be. So far, they have reported details on the data breaches at Yahoo, LinkedIn, and DropBox.
And of course, we’ll keep you updated here on CMS Critic if any other hacks or critical human errors occur at the expense of business software vendors – just like we did with the 123Reg disaster.
Have you had any security issues with Weebly over the last few months? Let us know in the comments section below.