Drupal Remote Code Execution vulnerability exploited widely

Re:Drupal Remote Code Execution vulnerability exploited widely by Angostura on Thursday April 26, 2018 @05:46AM (#16930394)

Ah yes, training up people to handcraft html every time a new press release needs to go up on the site, or a VP changes on thecabout us page. Not fun.

[ Parent | on HN ]

Re:Drupal Remote Code Execution vulnerability exploited widely by empath75 on Thursday April 26, 2018 @08:25AM (#16931193)

There are apps that generate static websites.

[ Parent | on HN ]

Re:Drupal Remote Code Execution vulnerability exploited widely by detaro on Thursday April 26, 2018 @08:15AM (#16931138)

By that definition, everything that has a WYSIWYG editor is an "enterprise CMS"?

[ Parent | on HN ]

Re:Drupal Remote Code Execution vulnerability exploited widely by setquk on Thursday April 26, 2018 @07:33AM (#16930920)

Hire someone to do it. Cheaper than an enterprise CMS is to run and/or commission.

[ Parent | on HN ]

Re:Drupal Remote Code Execution vulnerability exploited widely by Angostura on Thursday April 26, 2018 @08:14AM (#16931131)

Lets see, my Wordpress install running a well known theme, using Wordfence to alert for plugin updates, with me keeping an eye on it cost about £2,000 to set up and has ongoing costs of about £1,000 a year.

No. Its not cheaper to hire someone to hand-code the site and then hand-code every change.

[ Parent | on HN ]

Re:Drupal Remote Code Execution vulnerability exploited widely by setquk on Thursday April 26, 2018 @08:48AM (#16931356)

If you're doing that, just use wordpress.com. Wordpress is way out of scope for the term "enterprise CMS".

[ Parent | on HN ]

Re:Drupal Remote Code Execution vulnerability exploited widely by Angostura on Friday April 27, 2018 @01:36PM (#16942621)

So we've gone from "there's no need for a CMS, write HTML flat files" to "Use a hosted CMS" - OK.

[ Parent | on HN ]