[{"data":1,"prerenderedAt":11},["ShallowReactive",2],{"$f3g405d0ozo8tp":3},{"slug":4,"title":5,"description":6,"published":7,"updated":8,"thumb":9,"html":10},"securing-wp-config-php","How to Secure wp-config.php File in WordPress","Securing wp-config.php You can move the wp-config.php file to the directory above your WordPress install. This means for a site installed in the root of...","2016-06-17","2017-04-25",null,"\u003Cp>Securing wp-config.php\u003Cbr \u002F>\nYou can move the wp-config.php file to the directory above your WordPress install. This means for a site installed in the root of your webspace, you can store wp-config.php outside the web-root folder.\u003C\u002Fp>\n\u003Cp>Note: Some people assert that moving wp-config.php has minimal security benefits and, if not done carefully, may actually introduce serious vulnerabilities. Others disagree.\u003Cbr \u002F>\nNote that wp-config.php can be stored ONE directory level above the WordPress (where wp-includes resides) installation. Also, make sure that only you (and the web server) can read this file (it generally means a 400 or 440 permission).\u003C\u002Fp>\n\u003Cp>If you use a server with .htaccess, you can put this in that file (at the very top) to deny access to anyone surfing for it:\u003C\u002Fp>\n\u003Cp>\u003Cfiles wp-config.php>\u003Cbr \u002F>\norder allow,deny\u003Cbr \u002F>\ndeny from all\u003Cbr \u002F>\n\u003C\u002Ffiles>\u003C\u002Fp>",1793901039234]