6 ms·
WordPress plugin hole puts '2M websites' at risk
- hbcondo714 4y agoThis is regarding the Advanced Custom Fields plugin which has 2+ million active installs according to the WordPress plugin page: https://wordpress.org/plugins/advanced-custom-fields/ https://wordpress.org/plugins/advanced-custom-fields/
- devmor 4y agoIn the past, I have worked in a couple different multi client firms that handled a lot of WordPress installs and I think every single one of them used ACF. It's also had many major security issues like this. I vaguely remember another one that was nearly as ubiquitous and constantly causing people to get hacked - had a very generic name like "Contact Form 2000" or something.
- gjsman-1000 4y agoContact Form 7?
- devmor 4y agoThat's the one! I had the number wrong.
- chiefalchemist 4y agoTo your point "The vast majority of bloggers and small business owners that run WordPress sites … are not cybersecurity experts," Ellis said. That audience is also unlikely to use ACF.
- devmor 4y agoNo, they are quite likely to be using ACF... and not even know that they are using it. The majority of these folks pay someone to set up their website and then never touch it again until something breaks. This was the primary reasoning behind WordPress forcing automated updates.
- Dalewyn 4y agoThe tech industry more or less refuses and denies with the fury of a thousand chimpanzees the reality that common men only see computers and the things they provide as fixed appliances.
- kyriakos 4y agoMost wordpress sites are setup by web "designers". Install as many plugins needed to get the job done along with a theme. Usually follow tutorials for most things which are often outdated. If the tutorial suggests ACF then ACF is installed. Unsuspecting client recieves site with zero knowledge of what they are getting into. Especially a problem if any customization is made to plugins blocking them for automatically updating.
- chiefalchemist 4y agoI do agree. ACF is indicative of site owner hiring someone else to do the design / build. The rest, I see it different. Most WP sites are self-setup (read: for "free") by the site owner. ACF has 2M installs. That's a fraction of total WP sites. Therefore, I conclude most WP site aren't setup by "designers".
- Ayesh 4y agoI occasionally working with WordPress sites, and I personally find ACF plugin as a smell when someone tries to bend WordPress into what it already is not. Pretty much 100% of compromised WordPress sites I get are caused by a plugin like this, be it either a configuration issue or a vulnerability in code.
- lagniappe 4y agoI've been out of touch for a while now in the CMS field; is Wordpress considered the default CRM in 2023?
- devmor 4y agoWordPress has been and remains the default CRM since the inception of free/low cost hosting. The ease and low cost of multi-tenant PHP environments combined with the incredibly massive resource base of themes and plugins basically makes it unstoppable for anyone needing something more than what Squarespace can offer in a budget web platform. The fact that it can be shoe horned into doing so much at an "acceptable" level of quality makes it a nearly unkillable zombie.
- lmm 4y ago> WordPress has been and remains the default CRM since the inception of free/low cost hosting. Not quite. In the very distant past Movable Type was the incumbent and WordPress was the scrappy upstart trying to displace it.
- markdown 4y agoJoomla was the leader in CMS’s for a long time, until WP broadened it’s target market away from just blogs.
- lagniappe 4y agoI think drupal was a thing for a while too, but it didn't make much sense to me at the time.
- devmor 4y agoDrupal was very popular for people who reached the limits of what WordPress could do.
- 12907835202 4y ago
- 1letterunixname 4y agoIt's ancient PHP. What do you expect? Hell, Facebook doesn't even use PHP anymore having replaced it with a pseudo-superset, Hack. If you want security, don't cargo-cult what everyone else is doing or use third-party code. Third-party code in dynamic languages is footgunning in a mine field. Easy || popular != sustainable
- berkle4455 4y ago> It's ancient PHP. What do you expect? It's an XSS vulnerability. There's 22,329 XSS CVE's across every language and platform you can imagine. https://www.cvedetails.com/vulnerability-list/cweid-79/vulnerabilities.html https://www.cvedetails.com/vulnerability-list/cweid-79/vulne...
- woodruffw 4y agoThe question isn't what you or I expect; it's what non-technical people who administrate a WP site that was set up for them might reasonably expect.
- EdwardDiego 4y agoPfft, I can write insecure code in any language.
- graypegg 4y agoIf you can’t FootGun.shoot(Foot) then are you really free?
- deafpolygon 4y agoAren't you the one cargo-culting by saying PHP is ancient? It has nothing to do with "ancient". PHP is still a very strong language to be using even now - sure it isn't what the cool kids are using, but it is hardly ancient. Third-party code is everywhere. What are you on about?
- code_duck 4y agoI assumed GP meant WP was PHP written a long time ago, not that the language is ancient or obsolete. Whether that’s accurate (has the WP code base been revised much?), I have no idea.
- EnigmaCurry 4y agoIf you are stuck on wordpress, consider using a static export plugin like wp2static [1]. I have been playing around[2] with a setup where the normal WP UI is protected behind HTTP Basic Authentication, and wp2static exports the public snapshot [1] https://github.com/WP2Static/wp2static https://github.com/WP2Static/wp2static [2] https://github.com/jessopb/wp_d_rymcg https://github.com/jessopb/wp_d_rymcg
- throw0101b 4y ago* https://wordpress.org/plugins/simply-static/ https://wordpress.org/plugins/simply-static/ * https://wp2static.com https://wp2static.com
- snowwrestler 4y ago> On May 5, a month after a patched version of the plugins was released by Delicious Brains, Patchstack published details of the flaw. It's recommended users update their plugin to at least version 6.1.6. Emphasis mine. It is not actually that hard to run Wordpress securely. Stick to supported plugins and themes, and install security patches quickly when they are released. The vast, vast majority of WP attacks are based on known vulnerabilities, and only start after the details are disclosed. The bad guys who bother targeting WP are generally lazy and unsophisticated. Obviously if you know you are a high value target, you may want to stand up additional defenses.
- SllX 4y agoThanks. For a moment I thought this was 2007.
- safety1st 4y agoTo add to this advice, you can enable auto-updates for any WordPress plugin with one click. Anyone who enabled auto-updating for ACF would not be affected by this vulnerability. If a site is not mission critical or you don't have the time/budget to maintain it, just enable auto-update on everything. This will protect you from the vast majority of vulnerabilities. There is a very small chance an auto update may break something on the site. If a site is mission critical, every 1-3 months you should take a backup, update manually, and do some testing to verify that nothing broke. It's not rocket science and not particularly difficult or expensive. There is a proposal to make auto-updating the default. But because WordPress has to support everything from millions of personal blogs to whitehouse.gov, a proposal like that is a complicated topic. Notably whitehouse.gov has never been hacked.
- e12e 4y ago> Anyone who enabled auto-updating for ACF would not be affected by this vulnerability. Pedantic, but you would have been vulnerable if someone else also found the hole, but kept it secret? Sure, when an exploit makes into metasploit or gets published things are worse if you don't patch - but just because the barn door is closed now with a patch, it doesn't mean you were secure when there was a big hole in the door...
- ShadowBanThis01 4y agoplug-in hole
- Cloudef 4y agoIt's amazing WP is still used for sites that might as well be statically generated
- sumoboy 4y agoClick update on the plugin and it's done in 3 seconds. The responses to solving this problem are just toxic on this thread. No need to rebuild to a static site, headless cms, or some other cms. Like every NPM is absolutely perfect without security issues? Let's toss aside all the javascript frameworks and go back to static pages. I've found recovering WP sites from hackers one of the easier tasks to do, it's a pretty simple platform. Wordpress is a highly target platform for hackers regardless of what plugins are used. ACF is a really good plugin in the WP ecosystem.
- stevesearer 4y agoACF is from Delicious Brains which was acquired by WP Engine last year.
- pabs3 4y agoI wonder if Snuffleupagus can block this exploit. https://snuffleupagus.readthedocs.io/ https://snuffleupagus.readthedocs.io/