Yesterday i received an email from a guy that our site is vulnerable to SQL injection. The email said:
I need to know if there is any way of writing additional code to JavaScript files already deployed on the server.
I\'m building a webpart for a Sharepoint site that allows the user to enter information into a textbox that will eventually be showed to other users. The problem is that I need to allow simple formatt
Note: I\'m using Zend Framework, but I think most of this applies to PHP coding in general. I\'m trying to choose a strategy for writing views scripts, possibly with the help of a templating engine.
I\'ve implemented a PDF generation function in my flex app using alivePDF, and I\'m wondering if the process I\'ve used to get the file to the user creates an XSS vulnerability.
In your experience, what have you found, worked on, or encountered in terms of site vulnerabilities? And what actions did you take to mitigate these issues?
We got a long-running website where XSS lurks. The problem comes from that some developers directly - without using HtmlEncode/Decode() - retrieve Request[\"sth\"] to do the process, putting on the we
I\'m working on an app that would allow people to enter arbitrary URL\'s that would be included in <a href=\"ARBITRARY URL\"> and <img src=\"ARBITRARY URL\" /> tags.
Ok, so I have been reading about markdown here on SO and elsewhere and the steps between user-input and the db are usually given as
I have a Web application and have run a XSS scan on it and it reports that one of my pages that has a Java applet in it could potentially be open to XSS.