Addressing the WordPress Is Not Secure by Default Argument

Addressing the WordPress Is Not Secure by Default Argument WordPress being an open source script has its code publicly available. It means anyone willing to contribute can build on top of others’ work. This is how WordPress software gets developed. The WordPress security team cannot always be on top of security vulnerabilities because it is difficult to address something which is not even discovered yet.
Some people say that WordPress has built in features which are not inherently secure which some day end up plaguing the site security. Careful there. This is not what I said; it’s a speculation that I have had read many times over. You must be wondering why these known vulnerabilities are not fixed in the first place? Core developers must devise a plan to fix issues like WordPress version number, limiting login attempts, etc. But, that’s not the case, is it? So, there must have been a strong reason for not doing it till now. I believe it is not as simple as it sounds.
That’s what I want to address today. The fact that WordPress is secure. The argument about WordPress is not secure by default is way off. In this post, you will learn how hackers attack WordPress
Source: https://managewp.org/articles/13506/addressing-the-wordpress-is-not-secure-by-default-argument

source https://williechiu40.wordpress.com/2016/09/30/addressing-the-wordpress-is-not-secure-by-default-argument/