Protect and lock down your WordPress media files

Hello!

Occasionally it was necessary for us to lock down some or all of the WordPress media library from public viewing, indexing. The reasons why this would be necessary can vary from sensitive information leakage to private user information protection (i.e. custom user media files uploaded on a per user account basis).

Either way, there is a relatively straightforward way to lock down the visibility and permissions of files or folders in your media library from either being indexed (And disclosed more easily to the public for access) or randomly accessed through browsing the wp-content/uploads folder. Remember this folder usually (by default) has directory index enabled. This means you can usually visit a WordPress site, manually access the site.com/wp-content/uploads folder and browse the files and folders therein in order to see if any sensitive information is contained within.

Sometimes its not enough to simply edit your robots.txt to not allow Google and other search engines to index your site. Having a sensitive PDF or Word document show up in google results is obviously not ideal, however it is very trivial for someone to manually scan your uploads folder to enumerate any sensitive documents which increases risks like information disclosure and confidentiality issues.

How would we address this? The solution I would propose here is twofold : Modify the default uploads destination folders to include logic to separate media uploads for custom content or media that is uploaded on a per user basis into separate folders. Doing this will lay the groundwork for us to restrict media that is uploaded under certain conditions.

Change Media Upload Default Folder

There are many methods to accomplish this. One way would be to modify your theme’s functions.php file to include code to modify the upload folder based on certain conditions. Those conditions could be if the user belongs to a specific role / group or if the hey a specific capability :

You can see with the above snippet that anything can be possible with this. To check for a specific role, you simply can access the global variable $current_user and check what the assigned role is :

This will make the foundation of all the changes we’ll make later on to lock down the WordPress media folder. Now another option to accomplish all of this, if you’re less PHP inclined, would be to simply install a plugin to do all the work. A great plugin to accomplish the same thing as the above would be the Custom Upload Dir plugin.

This plugin adds an option to your administrative interface to manipulate the default uploads folder. This is a great plugin because it allows you to use placeholder tags to create a truly unique and predictable upload directory structure :

The keyword here is predictable. We will eventually be building logic into WordPress to set a session cookie if the user belongs to a User Role/Group. Then we will tell Nginx or Apache to refuse direct file access to those folders if the cookie is not present.

So lets say we had a custom post type called “custom-content” and we wanted to protect all of the media uploaded only for that content. Using the above plugin, we would configure a custom upload directory like the following :

So what would that do? If I uploaded a media file for my custom content called “custom-content” then it would be located in the following folder :

Having a predictable URI structure means that we can tell Nginx or Apache to perform certain conditional checks based on the URI path. We’re not there yet! We need to set the session cookie first.

Set a session cookie to protect WordPress media

There may be plugins to accomplish setting a custom session cookie but I prefer to do it custom in functions.php because it will allow me to set all the options. This is especially useful when we are dealing with custom content + custom session cookies. Plugins can only be so versatile and flexible before (usually) coming short of what they need. If they dont fall short, then the extra features you need are in a “premium” version of the plugin.

So lets define a function in functions.php and add it to the init hook to create the cookie :

Whats going on here? Well we’re just triggering a custom function on WordPress init to create a session cookie (if it doesn’t already exist) called custom_cookie. This cookie is ONLY set if the logged in user belongs to the custom role called “Whatever”. You can see the possibilities here. We can set any condition we want, the possibilities are endless. This again is the advantage of implementing your own code instead of finding a plugin.

Okay lets recap what we’ve done so far :

1. We defined a custom uploads directory which identifies a predictable folder structure that will allow us to create a check in Nginx or Apache for a specific session cookie

2. We create and apply a session cookie if the logged in user meets specific conditions

Configure Apache or Nginx to check for the cookie if the request URI matches

Just like the title says, we want to tell Nginx or Apache to check for that session cookie if a user tries to request a file that matches the path in question. Remember the key here is that session cookie wouldn’t be present if the conditions didn’t match in our functions.php. Additional security to prevent cookie forgery could be implemented such as specific values in the cookie value that can be verified such as authentication or user ID values. I’ll leave that up to you because if you’ve made it this far, you should be able to investigate additional secure methods of implementation beyond the basic overview provided here.

For Nginx , here is a sample configuration directive you could try as a starting point :

In the above config directive snippet, we are checking for the presence of the custom_cookie cookie (and if it has a value of “2” , which could be anything). This cookie check only happens if the URI path matches /wp-content/uploads/custom-content. You can use more fancy Regex to match author names or whatever combination of conditions that suits your needs.

For apache, we will be doing something similar with Rewrite rules :

In both the Apache and Nginx examples, we are doing a 301 redirect to the homepage if the condition match fails. The advantage of not providing a 403 forbidden or 500 series error is that the end-user (unless they pry or manipulate host headers or cookies) will not be able to easily see what happened. They will just know that they attempted to view a file and were redirected to the homepage. If a 403 forbidden error was provided then they may be more inclined to pry further and it would be easier for them to differentiate accessible files from inaccessible files for penetration testing purposes.

I hope this guide helps!