With all of the recent talk about WordPress security and Nonces, I've decided to create a plugin that enhances the security.
It is meant to both provide an easy way for some users to disable the referer check without giving away the house, and as a way to provide enhanced security for those that can use the referer check.
- Enables/Disables Referer check (Disabled by default)
- Adds an optional "One IP per Admin Session" check (Disabled by default)
- Times out sessions after inactivity (10 Minutes by default)
- Posting - which takes longer - has a different time out period (30 Minutes by default)
- All features are configurable on a plugin options tab
I'll probably run my times at 5 & 30 minutes with the IP check on, but I'll have to do more use testing first.
This is the alpha release and includes no documentation. Just extract it with paths to your plugin directory, activate it and look for the new configurations tab under the plugins directory. That said - if you didn't know that, you shouldn't be running the alpha release. This has been tested for one morning on one blog at this point and is my first ever WP plugin. I knew nothing about plugin writing yesterday morning. So, it is probably not ready for prime time. (That said it seems to work fine.)
Here's the link: http://www.TheCodeCave.com/downloads/plugins/sn4wp-alpha1.zip
So please take a look and tell me what you think. Does it work?
Notes taken while making this plugin...
What does the referrer check do?
Checks to see if an admin action was initiated from an admin page.
What is protected by the referer check?
Only certain actions are protected by the referer check.
The common thread seems to be that the action must be a single destructive step.
The protected actions include: (An * indicates it was added with verison 2.02)
Categories - Delete
Link Manager - Assign, visiblity, move, add, editlink, delete
Options - Update
Plugins - Activate, Deactivate
Posts - Post*, editattachment*, editpost*, Delete, deletecomment, unapprovecomment
Profile - Post
Themes - Activate, Deactivate
User-edit - Switchposts, update*
Users - Promote, dodelete, delete adduser
Additionally the akismet plugin's configuration page
Note that these actions consist of the the "final commit" steps. For instance the
"linkedit" action that brings up the form allowing you to edit a link is not protected.
However, the "editlink" action that posts the changes IS protected. Please keep this in
mind when testing this plugin.
Can a referrer be wrong?
Yes, many proxies strip or replace the referer. Additionally referers can be forged,
but the fact that a login cookie is also required makes such attacks difficult. The
referer check, when working CAN protect you from some attacks. That's why this plug
in does not disable it by default.
Can a referer check be simulated in a plugin? And if so how?
While we cannot check to see if each individual action came from an admin page, we
can ensure that an admin page was recently used by that user. If that user just
accessed an admin page, allow the action to succeed.
Problem: All action links change pages before taking effect. So the page last viewed
by the user by the time the admin referer check hits is ALWAYS an admin page.
Additionaly, the final post action involves multiple pages which would violates any
LastPage tracking scheme used in Nonces (even after you implement it).
Solution: Without access to the name of the action that is about to be attempted, the
nonce needs only indicate the previous page was an admin page. This can be
indicated by whether or not the Nonce is valid.
Problem: An admin could close their admin page without logging out.
Solution: The nonce times out after 5 minutes. They are vulnerable for 5 minutes if
they forget to log out.
Problem: An admin could leave the admin area and go back to their blog without
Solution: None - Admins often use one tab to admin their blog, and another to view it.
Likewise, the preview has a non admin context.