WordPress useful of safety devices to protect your plugins

Very likely something catastrophic to a webmaster or if your artwork and commitment are intruders, however, the INTRO GONE County. Online piracy is a phenomenon that is as old as the Internet always own this group of people who love what is the difference with other programs have built.

Protect Your Plugins

That is to blame for this, works as an analyst in security can be a very nice, with great reviews at the end of the month, as well as the ability to work with the latest technologies. WordPress has been more popular CMS for many years, and we agree that still dominate the market for at least a decade before us.

Market Share 2019 WordPress

The data of OpenSourceCMS and reflects only ~1% of adolescents in the market share of all content management systems of the instantaneous. However, the vast amount of market share of WordPress has collected over the years and leads us to our next section.

WordPress is the objective pursued by many hackers the hat Hat black and white. And in my opinion. A system that millions of webmasters use every day. I would like to draw your attention to this report, a review of security The security company check Marx has become more popular 50 plugins for WordPress and came to a conclusion is impressive.

In June 2013 the research laboratories of the verification of Marx executed several every new one security against the source code of the most popular plugins for WordPress. As a result? More than 20% of the 50 most popular plugins for WordPress are vulnerable to attacks such as SQL injection on a web page. A total of 8 million plugins for WordPress in danger have been eliminated. The present report contains the results of the research, as well as recommendations and risk mitigation measures for developers of plug-ins, Director General Website and supplier of platforms on the development and installation of the third-party extensions. [S].

Because WordPress is a community of open source, often impossible to check the condition of the safety of each plugin, no matter how hard the team works in the prevention of this high percentage of WordPress plugins for vulnerable. But if you are a developer and really plug-ins (or intend to do so in the near future), it might be a good idea to take a look at some of these features WordPress, vulnerabilities be avoided, and other security risks.

How can we protect our plugins for WordPress?

You can recline confirms that the Codex WordPress page contains no information about incisive and organization of security, but the desire of this post for something of a note for you, so, if you want to learn or actively the development of WordPress plugins; this could be a good use of your favorites to talk about the future.

Clean Activate your Debugging

As a developer, we often think of several things at the same time thanks to countless code files scouting and tried to find the errors seemed not to be there. All this we can make unwise and we forget some of the standard protection methods and analysis of our Code. If the asset itself.


Define('WP_DEBUG', true);
Define('WP__DEBUG DISPLAY', false).
Define('WP__DEBUG LOG', true);
Define debug('Script', true);
Define('WP_cache', false).

To do this, copy/paste in our wp-config.php we in our development environment. This enables us to live in the environment dev can consult all news error if it does not give us a headache, and above all wasted our time. It is very simple is widely ignored because of simplicity.

Disinfect all

The weak points of the security plus sanitization of your tasks, in particular with regard to the database user or discussion - input and output of the locations were more often hackers will try, records, and of possible attacks vulnerabilities.

intval();
absint();
wp_kses();
sanitize_title();
sanitize_email();
sanitize_file_names();
sanitize_html_class();
sanitize_key();
sanitize_meta();
sanitize_mime_type();
sanitize_option();
sanitize_sql_orderby();
sanitize_post_field();
sanitize_text_field();
sanitize_title();
sanitize_title_for_query();
sanitize_title_with_dashes();
sanitize_user();

WordPress offers a long list of tasks in sanitation, and all are easily referenced tasks in official documents - all I can say is that they are all self-explanatory view the database functions of WordPress.

Don't forget to escape

The data are not the confidence of many sources (the user of third-party Websites, the database own ! etc.) and validated is due to both input and output. It is better, the validation of the output as late as possible in the ideal case, at the time of exposure, in contrast to the top of the script. In this way, you can be sure that your data are correctly validated/fled and needs to remember when the variable previously confirmed.


esc_html();
esc_textarea();
esc_attr();
esc_url();

Your valid queries in the Database

Always made attention to the database, such as the query and if the query to properly clean and in order to reduce security risks.

$wpdb->insert();
$wpdb->update();
$wpdb->prepare();

Random data (nonces) WordPress

A nonce is a number used to protect "once" URLs and the forms of abuse. Invalid nonce causes for WordPress Send to a "403 Forbidden" response in your browser, with the error message: "You want to do?", a Nuncio adds it and the query string in a direction they can add URL in a hidden area in a form, or by other means.

wp_nonce_url();
wp_nonce_field();
wp_create_nonce();
check_admin_referer();
wp_verify_nonce();

All these features charming helps to approve and the protection of your URL of the IOSA malic acid mind attacked.

Curl! = for WordPress

It is advisable to observe the use of curl in your plugins for WordPress and is one of the best practices on the use of the functions of WordPress, aid to the safety hazards that curl with requests.

wp_remote_get();
wp_remote_post();
wp_remote_request();
current_user_can(); // last of our security functions

The tasks WordPress

WordPress is serious about security, as your own user base and your size. For this reason, there are many functionalities that we use to protect our plugins, local chapters and, therefore our plugins much more quickly and efficiently. As you can see in this post, it takes a little research in learning many exciting possibilities for our plugins and the safety of users. In short, it is the protection of our intellectual property and ensures that our users are protected and secure.

How to protect your own plugins for WordPress?