Comments on: Real WordPress Security https://ma.tt/2025/03/real-wordpress-security/ Unlucky in Cards Thu, 20 Mar 2025 09:56:27 +0000 hourly 1 https://wordpress.org/?v=6.9-alpha-60134 By: Andrei Chira https://ma.tt/2025/03/real-wordpress-security/#comment-603932 Thu, 20 Mar 2025 09:56:27 +0000 https://ma.tt/?p=140118#comment-603932 My experience is different. In almost 15 years of hosting WordPress websites, I’ve never seen a website infected or hacked because of a hosting security issue.

]]>
By: Snehasish Nayak https://ma.tt/2025/03/real-wordpress-security/#comment-603899 Fri, 14 Mar 2025 22:08:47 +0000 https://ma.tt/?p=140118#comment-603899 In reply to Adrianne.

This is exactly what happened with one of my sites in 2019. I was not in a position to invest in the cost, hence I had to take the entire site down, as it was showing malicious link everywhere.

That’s the reason, despite of all the discussions going around with Matt, and Automattic, I decided to stick to WordPress.com.

]]>
By: Adrianne https://ma.tt/2025/03/real-wordpress-security/#comment-603892 Thu, 13 Mar 2025 14:29:37 +0000 https://ma.tt/?p=140118#comment-603892 Sounds like a classic case of ‘paying for peace of mind’… but when things go wrong, you’re hit with even more fees. It’s crazy that a host’s security can cost you more than the site itself.

]]>
By: Anthony Zeoli https://ma.tt/2025/03/real-wordpress-security/#comment-603878 Mon, 10 Mar 2025 04:15:20 +0000 https://ma.tt/?p=140118#comment-603878 I’m fortunate to have planned wisely and all of the sites under my control over the last 15+ years avoided being hacked. I’ve fixed a number of hacks for others ober the years. Today, I personally update all my client sites individually and do not rely on auto updates or the roll back plugin. I feel that me being in tune to what is going on with those sites is important enough to DIY. And that’s why I pay more fory hosting plan to ensure I’m on a higher level of service than the shared resellers offer. Knock on wood, I’ve been able to avoid these issues and I’m able to clean a hack with instructions. I know many who have had to pay hosts who, like you wrote, are ultimately responsible for the intrusions. I’ll be bringing this up for discussion to our next WordPress Asheville Meetup a week from Tuesday.

]]>
By: Iqbal https://ma.tt/2025/03/real-wordpress-security/#comment-603877 Mon, 10 Mar 2025 03:04:24 +0000 https://ma.tt/?p=140118#comment-603877 Matt, do you remember in 2022 when WordPress.com changed its pricing to a single plan, the Pro plan? Thank you for providing a dedicated thread in the forum at that time to gather feedback from us, the WordPress.com users.

I appreciate that WordPress.com listened to those suggestions. In fact, I feel that all my feedback was addressed: creating a plan between the Pro plan and the free plan (Starter plan), setting pricing according to regions, offering monthly pricing, and providing à la carte options or add-ons (such as the option to add storage size)—everything was fulfilled. I’m very grateful for that.

When the pricing was reverted to the original structure, I’m still enjoying the legacy Pro plan. Thank you.

]]>
By: WP Weekly 233 - Themes - Offline AI+WP, Trademarks Done, 50K Users in 34 Days https://ma.tt/2025/03/real-wordpress-security/#comment-603876 Mon, 10 Mar 2025 02:15:18 +0000 https://ma.tt/?p=140118#comment-603876 […] on real cost of security for WordPress websites & […]

]]>
By: Bob Perkowitz https://ma.tt/2025/03/real-wordpress-security/#comment-603875 Mon, 10 Mar 2025 00:47:24 +0000 https://ma.tt/?p=140118#comment-603875 Matt… this is what WP is all about. Kudos and onward.

]]>
By: Josh Betz https://ma.tt/2025/03/real-wordpress-security/#comment-603874 Sun, 09 Mar 2025 21:40:21 +0000 https://ma.tt/?p=140118#comment-603874 […] Matt Mullenweg on WordPress security: […]

]]>
By: Snehasish Nayak https://ma.tt/2025/03/real-wordpress-security/#comment-603860 Sat, 08 Mar 2025 11:10:39 +0000 https://ma.tt/?p=140118#comment-603860 Happened with me twice, and I got literally got no help. And my site got hacked not because there was a vulnerability at my end, but because their shared hosting server got hacked.

Not naming the host, but it happened.

]]>