this post was submitted on 17 Oct 2023
92 points (100.0% liked)
Technology
37702 readers
274 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
“Smart WordPress sites”, now that’s an oxymoron!
But do please tell how you figure out if a plugin will be caught having a vulnerability or not.
The fact that you can audit it has zero value.
People don’t audit anything, and pretending that they do is hopeful at best, deceitful at worst.
Even if you audit it you are likely not understanding the code well enough to figure out if it is vulnerable.
Which leads back to my original point which thus still stands; there’s no smart way to choose non-vulnerable plugins. One can obviously avoid things that don’t meet certain standards (popularity, lines of code, known issues, how they’re resolved, etc.), but still doesn’t guarantee anything.
This means that your statement about “smart Wordpress sites don’t pick vulnerable plugins” is frivolous. May I suggest “smart Wordpress sites chooses plugins carefully and limits the amount to those strictly necessary, but should still pay attention to updates patching issues”. Because that’s the difference between smart and dumb. Dumb sites are just left running whatever they shipped with, PHP or not, and smart devs make sure to keep their system and/or CMS and plugins up date.
And if you still want to argue that people actually review the code they depend upon I have one word for you: Heartbleed.