-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential XSS issue with add_query_arg() and remove_query_arg() #39
Comments
Hi Quassy, |
I don't think so. As I understand it the two functions were never meant to escape their inputs / outputs. It was a bug in the documentation which led plugin developers to falsely assume it does and resulted in implementing this security hole unknowningly.
Release notes / blog posts of 4.2 and 4.1.3 don't mention that the issue was fixed, while 4.1.2 mentions it and calls on developers to fix their plugins. |
VERY risky stuff. |
I am by no means a WordPress or plugin developer, so take this with two spoons of salt and pepper!... I don't actually know what's happening with
1327:
1339:
So basically adding ´esc_url()´ every time the URL might be printed somewhere and adding ´esc_url_raw()´ every time the URL is used for a header. |
Well, let's hope someone who knows more then both of us will give this a look :) Thank you very much for the report! 👍 |
As you may know quite recently there was news that WordPress plugins could suffer from a XSS vulnerability if they use
add_query_arg()
andremove_query_arg()
without properly sanitizing the data. When the optional third parameter of these functions is omitted,$_SERVER['REQUEST_URI']
is used unescaped, more info here.Checking your source it seems the functions are used in the following lines of feedwordpress.php:
I am not actually sure if FeedWordPress is vulnerable but I think it should be looked at and
esc_url()
oresc_raw_url()
be added.The text was updated successfully, but these errors were encountered: