Not quite following. The XSS stuff should already be published and available in the current release of the plugin.
Anything with permalinks is taken as a per-user case because there’s no one single source of issue with rewrite rules. If there was some widespread bug, I’d be a lot busier right now 😛
hi,
thanks for your reply.
ok – i guess i’m in the scope of “a per user” that the update did not do well with… 🙁
that is why i asked if you could only inform what to change & in which file to take care of the XSS issue (i will remain with previous version but withot XSS vaulnarbility…)
hope i got it clear this time -:-)
thanks a lot
Not really, sadly.
Ultimately what are you trying to accomplish here? Fix an XSS vulnerability? Because that’s not related to users having issues with permalinks after an update. The update for the “Fixed potential XSS issue.” was in version 1.1.2, and is NOT a per-user case. If you have 1.1.2, you are already receiving fixes for it. Issues with permalinks are per-user, and it’s not related to the XSS part.
If you’re on version 1.1.2, you have the XSS fixes already. If you are having issues with permalinks, that’s unrelated and we can continue on debugging that issue here.
ok, i guess i forgot to mention that i’m on 1.0.7…
i didn’t update for a long time.
as is (1.0.7) works GREAT for me, i only want not to have XSS vulnerability issues..
that is why i asked if it is possible to guide me just for that fix.
unless it requires to update to 1.1.2. i would like to be able to stay on 1.0.7 but without the vulnerability issue.
hope you get my point 🙂
thanks
