Super Cache working fine, but install required wp-content chmod 777 (5 posts)

  1. circuitor
    Posted 8 years ago #

    My question is this: Is it a security risk to have the wp-content folder with chmod of 777?

    These sites seems to indicate that it was a security problem.

    But, the messages I got during install of wp-super-cache required the chmod 777 or it would not run. What do you think?

    Thanks for any information!

  2. Donncha O Caoimh
    Posted 8 years ago #

    Of course, there is a risk. The cache plugin will work fine if wp-content isn't writeable but you won't be able to change any of the settings.
    I need to do some testing of this to figure out what can be set to 755 and what needs to be 777, and when. The config file needs to be writeable but it might be ok to make wp-content 755 after the file is created.

  3. ateam
    Posted 8 years ago #

    I think your issue is the OWNER of wp-content.

    You DO NOT WANT chmod 777! I would only go as far as 775.

    So, wp-content needs to "chown apache" (or whatever is the appropriate user for your system).

    You could get away with "chgrp apache" with the chmod 775.

  4. After you get it setup and working, you don't need to leave wp-content at 777. You just need to leave the cache directory itself writable. Change wp-content back to 755 or 644.

  5. BlakkJakk
    Posted 8 years ago #

    Ateam, some of us our noobs from shared hosting. I think you should specific that when you talk about changing the owner you mean that the admin needs to be logged into the ROOT access to change the owner premssions of the file or you will have to open a service ticket with your host.

    For me apache 775 worked on WP-Content.

Topic Closed

This topic has been closed to new replies.

About this Topic