And people still justify using it 'because it's easy and simple for non-tech folks.' The non-profit world is _riddled_ with it.

Another day, another OS vulnerability

And people still justify using it 'because it's easy and simple for non-tech folks.' The non-profit world is _riddled_ with it.

Another day, another Android vulnerability

And people still justify using it 'because it's easy and simple for non-tech folks.' The non-profit world is _riddled_ with it.

Another day another PDF/flash/etc exploit

And people still justify using it 'because it's easy and simple for non-tech folks.' The non-profit world is _riddled_ with it.

Another day another security breach of a major non-WP website

And people still justify using it 'because it's easy and simple for non-tech folks.' The non-profit world is _riddled_ with it.

It's one thing to have periodic vulnerabilities in fairly central technologies that have few alternatives, and whose developers take those vulnerabilities seriously.

It's another to consistently choose a technology that has visibly and consistently thrown security to the wind, leaves its users totally vulnerable, and has no reasonable fixes; especially when far, far more secure alternatives exist.

So no, I don't believe any of those are valid equivalencies. WordPress is not the 'right tool' for any job. And PHP itself is also culpable in similar fashion.

I'm sympathetic to the idea that WP need not be exposed when a site can be delivered with static files. That's a fair argument that I agree with. But no one's advocating abandoning IOS or Windows or Android because if you install a certain app, or if you use a browser or open a certain type of file you run the risk of exploits. To advocate the throwing out the baby with the bathwater over a bug like this suggests you cherry pick your concerns and/or have an axe to grind.

WordPress is simple to set up, simple to use, and has a huge community. In the real world, it is often the best choice.