Normally it's a better practice to inform the site owner about a possible bug on their website and ONLY release it to public 'after' the owners have fixed it. You can also file cert advisories so that other webmasters using the software can get security patches.
What you did in this case was probably not the right way to expose the vulnerability. I am happy to know that you were curious enough to try the XSS vulnerability but making it public was not the best step.


LinkBack URL
About LinkBacks
Reply With Quote




Bookmarks