The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
Implementing CSRF Protection in modifications
With the new version released today for vBulletin 3.6.10 and 3.7.0 RC4, a new protection against Cross Site Request Forgery (CSRF) has been introduced. This new protection might influence the coding in modifications. Scott MacVicar took the time to compile a short explanation on this new protection for the coders on vBulletin.org: Changes for CSRF protection with third party modifications Cross Site Request Forgery (CSRF) involves taking advantage of the stateless nature of HTTP, there are no ways to ensure the exact origin of a request, its also not possible to detect what was actually initiated by a user and what was forced by a third party script. A token was added to the latest version of each of the vBulletin products, with the release of 3.6.10 and 3.7.0 RC4 it is no longer possible to submit a POST request directly without passing in the known token. The addition of a security token for each POST request removes the ability for a remote page to force a user to submit an action. At the moment this protection will only apply to vBulletin files and third party files will need to opt into this protection and add the appropriate hidden field. This was done to preserve backwards compatibility. Adding Protection to your own files To opt your entire file into CSRF protection the following should be added to the top of the file under the define for THIS_SCRIPT. PHP Code:
If this value is set to false then all CSRF protection is removed for the file, this is appropriate for something that intentionally accepts remote POST requests. You should always add this to your file, even if you don't think the script is ever going to receive POST requests. An absence of this defined constant within your files will result in the old style referrer checking being performed. Template Changes The following should be added to all of the forms which POST back to vBulletin or a vBulletin script. This will automatically be filled out with a 40 character hash that is unique to the user. Code:
<input type="hidden" name="securitytoken" value="$bbuserinfo[securitytoken]" /> Exempting Certain Actions It may be appropriate to exempt a particular action from the CSRF protection, in this case you can add the following to the file. PHP Code:
If the skip list needs to be changed at runtime is it available within the registry object, using the init_startup hook the following code would be used to exempt 'example.php?do=action_three'. PHP Code:
|
#12
|
|||
|
|||
=/ I dont get it, I have errors now too.. with RC 4
|
#13
|
|||
|
|||
What are the "forms"? and where do we edit them?
|
#14
|
|||
|
|||
everyone has errors ^^ by FORMS i think he means TEMPLATES. (style settings, etc)
|
#15
|
||||
|
||||
Quote:
A form is anywhere your users can submit data. If you have modifications that submit data and cannot update their templates then you need to post for support in the modification thread. It isn't hard to find out where this needs to go. In your Admin CP under Styles & Template select Search In Templates... Search for: value="$session[sessionhash]" In every template this occurs in add this line directly after the line containing the above, if it doesn't exist already: <input type="hidden" name="securitytoken" value="$bbuserinfo[securitytoken]" /> Save the template. |
#16
|
|||
|
|||
Thank you Wayne. :up:
|
#17
|
||||
|
||||
Quote:
|
#18
|
|||
|
|||
Is use your code but my ajax problem not solved !
2- Thanks Plugin Doesn't work again and it doesn't work on this mod . i have a question to vBulletin Core Dev Team : Sorry , Did you thinking before release a version perfectly ? because about the 98% percent of the forums i think use the many mods and with your advices no thing gonna change! because no body can modify the all form ! |
#19
|
||||
|
||||
Have you even read the first reply to the thread regarding AJAX requests?
|
#20
|
|||
|
|||
Quote:
Quote:
|
#21
|
|||
|
|||
thanks
|
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|