This is really easy (patch attached) - if there is jsonp_callback query attribute available - wrap json response into callback function specified by this attribute.
| Comment | File | Size | Author |
|---|---|---|---|
| jsonp-callback.patch | 1.05 KB | pavel.karoukin |
This is really easy (patch attached) - if there is jsonp_callback query attribute available - wrap json response into callback function specified by this attribute.
| Comment | File | Size | Author |
|---|---|---|---|
| jsonp-callback.patch | 1.05 KB | pavel.karoukin |
Comments
Comment #1
pebosi commentedHi,
would'nt it be better not to print $_GET['jsonp_callback'] without filtering.
Regards
Comment #2
antwanvdm commentedI think you should always filter input that could be manipulated by users. You think that might be the case in this situation?
Comment #3
oskar_calvo commentedthe patch works?
Oskar
Comment #4
pavel.karoukin commentedValid point with xss. I am no longer working on a project which used this module. Could someone try to wrap $_GET['json_callback'] into check_plain() before outputting and see if this close xss hole?