Title: wp-super-cache security issue (wp-content writable?)
Last modified: August 18, 2016
---
# wp-super-cache security issue (wp-content writable?)
* [fkranjce](https://wordpress.org/support/users/fkranjce/)
* (@fkranjce)
* [18 years, 10 months ago](https://wordpress.org/support/topic/wp-cache-3-2/)
* Hi,
* After many problems with CPU load of my server i’ve instaled wp-cache and it
works great. CPU load is down and site works extra fast.
* I have jsut two questions.
* I’ve look cached html files and i see adsense script is intact so i guess it
shoudl work fine and google wont have any problesm with cache.
* Second is about security. Wp-cache require 777 permision on content folder and
i am jsut wondering if it is possible to change that and keep wp-cache working.
I dont feel safe with 777 permision on that folder.
* Thank you for any help.
Viewing 10 replies - 1 through 10 (of 10 total)
* [dj-primat](https://wordpress.org/support/users/dj-primat/)
* (@dj-primat)
* [18 years, 8 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600415)
* +1
* [huckmag](https://wordpress.org/support/users/huckmag/)
* (@huckmag)
* [18 years, 5 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600433)
* bump for this. I just got spam files added to my wp-content folder and I’m pretty
sure it’s because of chmodding it to 777 for wp super cache.
* Any help on this?
* Moderator [Samuel Wood (Otto)](https://wordpress.org/support/users/otto42/)
* (@otto42)
* WordPress.org Admin
* [18 years, 5 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600434)
* The content folder does not need to be 777. The cache folder does.
* [huckmag](https://wordpress.org/support/users/huckmag/)
* (@huckmag)
* [18 years, 5 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600435)
* If I set the wp-content folder to 755 then in the wordpress admin section the
page for wp Super cache displays:
* **Error: wp-content directory (/hsphere/local/home/huckftp/huckmagazine.com/wordpress/
wp-content) is not writable by the Web server.
Check its permissions. Cannot
continue… fix previous problems and retry.
* Moderator [Samuel Wood (Otto)](https://wordpress.org/support/users/otto42/)
* (@otto42)
* WordPress.org Admin
* [18 years, 5 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600436)
* Well, that really sucks. Seems like an error in WP-Super-cache to me. It should
not require that wp-content be writable, it should only require that the config
file be writable (since that’s all it’s writing to).
* [huckmag](https://wordpress.org/support/users/huckmag/)
* (@huckmag)
* [18 years, 5 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600437)
* I *think* it’s still caching OK but the admin is not available.
* [Mark](https://wordpress.org/support/users/mindstar/)
* (@mindstar)
* [18 years, 5 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600438)
* Once you have WP_Super_Cache installed and operational, you can CHMOD wp-content
back to 755 (to protect your plugins folder).
* You will need to modify the wp-super-cache/wp-cache.php file to remove the check
to see if wp-content is writable.
* Comment out lines 723-726
* ```
if ( !is_writable($dir)) {
echo "Error: wp-content directory ($dir) is not writable by the Web server.Check its permissions.";
return false;
}
```
* [huckmag](https://wordpress.org/support/users/huckmag/)
* (@huckmag)
* [18 years, 5 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600440)
* The new version of Super Cache now displays the admin page even if you have wp-
content at 755 but it is read only.
* I now change it to 777 when I need to clear the cache or make changes in admin
and change it back.
* The new version is **0.5.4** and can be downloaded from
[http://ocaoimh.ie/wp-super-cache/](http://ocaoimh.ie/wp-super-cache/)
* [Jer Clarke](https://wordpress.org/support/users/jeremyclarke/)
* (@jeremyclarke)
* [18 years ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600461)
* I have to say: Still, WTF? The only file that needs to be edited to change the
settings is wp-cache-config.php, so why should people change the permissions
on both that AND wp-content when they want to change settings, rather than just
wp-cache-config?
* If Donncha is around, I’m interested to hear the reasoning, is there something
we’re missing? I guess we should just learn to edit the wp-cache-config.php file
manually?
* [myhelipad](https://wordpress.org/support/users/myhelipad/)
* (@myhelipad)
* [17 years, 10 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600472)
* I just install WP Super Cache 0.6.5 and running smooth but having warning when
i check back on WP Super Cache Manager
* > Cache contents
> Warning: Invalid argument supplied for foreach() in /home/xxxxxxx/public_html/
> wp-content/plugins/wp-super-cache/wp-cache.php on line 942
* pls advice.
* Regards
Viewing 10 replies - 1 through 10 (of 10 total)
The topic ‘wp-super-cache security issue (wp-content writable?)’ is closed to new
replies.
* In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
* 10 replies
* 7 participants
* Last reply from: [myhelipad](https://wordpress.org/support/users/myhelipad/)
* Last activity: [17 years, 10 months ago](https://wordpress.org/support/topic/wp-cache-3-2/#post-600472)
* Status: not resolved
## Topics
### Topics with no replies
### Non-support topics
### Resolved topics
### Unresolved topics
### All topics