Title: Security limitations w/ WordPress
Last modified: August 18, 2016

---

# Security limitations w/ WordPress

 *  [chrisjscott](https://wordpress.org/support/users/chrisjscott/)
 * (@chrisjscott)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/security-limitations-w-wordpress/)
 * My apologies if this has been answere or not… I’m considering WordPress for our
   small company’s extranet, where we’d be postig files for client review. I like
   the levels of security for posting, as I undertand them, but I’m looking for 
   something extra and can’t decipher whether or not WP offers this:
 * What I’d REALLY like is a front-end that prompts for a login when you first hit
   the blog and, based on the log in, shows content specific to that login. Obviously,
   I’m interested in only showing postings relevant to a particular client, based
   on that client’s login.
 * Is WP capable of this, either out of the box or w/ plug-ins? If not, do any of
   you blog-savvy folks have a suggestion for what might fit that bill? Thanks in
   advance…

Viewing 5 replies - 1 through 5 (of 5 total)

 *  [Cypher](https://wordpress.org/support/users/cypher/)
 * (@cypher)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/security-limitations-w-wordpress/#post-168678)
 * I don’t believe WP will do what you require it to do out of the box. And frankly,
   I don’t think you should even be looking towards a blogging software. A CMS (
   content management system) software like [PostNuke](http://www.postnuke.com),
   [PHPNuke](http://www.phpnuke.org), etc., might be more in line with what you 
   need.
 * They have greater control over user abilities and visibilties. You can restrict
   access to sections based specifically on usernames and so on.
 * Regards
 *  [Michael Adams (mdawaffe)](https://wordpress.org/support/users/mdawaffe/)
 * (@mdawaffe)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/security-limitations-w-wordpress/#post-168686)
 * You could try putting:
    `auth_redirect();` directly below the line including 
   wp-config.php in the file wp-blog-header.php. That’s an authorization function
   built in to WordPress. It shoud force people to log in before viewing any content(
   if they’re already logged in, a cookie will have been set and they won’t have
   to log in again). You can then figure out their user ID and customize content
   accordingly.
 * It worked for me in a quick test. No guarantees on how robust it is, but I think
   it will work.
 *  [dkdheensaw](https://wordpress.org/support/users/dkdheensaw/)
 * (@dkdheensaw)
 * [20 years ago](https://wordpress.org/support/topic/security-limitations-w-wordpress/#post-169333)
 * I am also interested in finding a way to require users to login to the main Blog
   page before viewing any content. I couldn’t get the auth_redirect(); line to 
   work. Can you please provide me with more information on this. Thx
 *  [obeattie](https://wordpress.org/support/users/obeattie/)
 * (@obeattie)
 * [20 years ago](https://wordpress.org/support/topic/security-limitations-w-wordpress/#post-169334)
 * Plugins, plugins, plugins!
 * Check out:
 * [http://17thdegree.com/archives/2005/07/01/wordpress-plugin-page-restriction/](http://17thdegree.com/archives/2005/07/01/wordpress-plugin-page-restriction/)
 * Cheers,
    Oli
 *  [obeattie](https://wordpress.org/support/users/obeattie/)
 * (@obeattie)
 * [19 years, 12 months ago](https://wordpress.org/support/topic/security-limitations-w-wordpress/#post-169335)
 * Coupled with that plugin – the thought just hit me that you can use if(user_level
   >5) or something along those lines. Look it up

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Security limitations w/ WordPress’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 5 replies
 * 5 participants
 * Last reply from: [obeattie](https://wordpress.org/support/users/obeattie/)
 * Last activity: [19 years, 12 months ago](https://wordpress.org/support/topic/security-limitations-w-wordpress/#post-169335)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics