ByDan Knauss
Posted on
Wordfence has a created a whitepaper aimed at developers and security researchers to share how coding flaws can introduce some of the most common and significant WordPress vulnerabilities — and how to prevent them. 🔒
WordPress 4.2.4 was released and auto-updated in the last 24 hours, thankfully to seemingly little attention (other than perhaps a bit of update fatigue). And that’s a good thing. According to the announcement post, the release addresses six different issues. The most interesting thing I learned with this release is from a comment Gary Pendergast…
In my blog post about today’s coordinated plugin update, I discussed the logistics of many of the top WordPress plugins working together to put out an update to fix the misuse of add_query_arg() and remove_query_arg(). Throughout the day, I’ve tracked other plugins as they update, and my list has around 35 plugins on it — and…
What if the way we talk about WordPress security focused on public acknowledgement of the security team members’ work, goals, and successes?
Matt Mullenweg did an AMA on Product Hunt. There’s not a ton you haven’t seen, but apparently there’s a new WordPress mobile app that’s still in “internal” beta. I wonder if it’s using the new REST API? I hope it’s not WP.com’s…. Also the “internal” label brought emotions that spilled into ill-formed words and I deleted…
All of your websites are ready for updates. There is a security and maintenance release ready for WordPress 3.8.2 and WordPress 3.7.2. It’s being released for both 3.7 and 3.8 due to the auto-updating feature released in WordPress 3.7. One of the items updated was to address the processing of pingbacks. The fix is identical…
Increase your chances of getting hired with these 5 tips: from knowing where to look to how to follow up after an interview.
