3 ms·
There are particular ways in which Wordpress exacerbates this situation. For example, let's say one of your $10 an hour freelance authors uses an insecure pass
by patio11 15y ago
There are particular ways in which Wordpress exacerbates this situation. For example, let's say one of your $10 an hour freelance authors uses an insecure password. What happens? Content defacement? Much of the time, the answer is arbitrary code execution, because Wordpress has had copious local-to-Wordpress privilege escalation vulnerabilities and, once they're admin, they can upload arbitrary PHP to your web server straight through the site.
Or let's say you allow anybody to sign up and comment on your blog. What's the downside risk, pesky comments? Nope, arbitrary code execution, because anonymous one-off commenters get an admin area and it has had copious local privilege vulnerabilities to turn them into real admins and then it is off to the races.
Then there is the XMLRPC library. Wordpress ships with it on by default. What's the risk of leaving it on? Say it with me, arbitrary code execution, because...
And PHP encourages you to do includes, including (when an edge case gets missed) inclusions of remote files (!), which puts you at risk of...
I mean, I love Wordpress. Never point it at someone you don't want to kill, always treat it like it is loaded, and keep it in a locked case, and you're mostly pretty much safe.
- dotBen 15y agoI'm not aware of any unpatched vectors to perform arbitrary code execution in WordPress Core. Sure perhaps via a dodgy plugin (and then ok you could run a SQL query directly to change the privilege level of a given user). XMLRPC ships in an 'off' state in WordPress, and has done for some time now. You need a copy of Dr dotBen's "How I learned to stop worrying and love the WordPress", published by WP Engine! ;)