Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

It looks like you don't escape content of submissions, allowing XSS attacks to be made.


sort by: page size:

Supposedly prevents XSS attacks via submitted HTML.

Ehh.. that's some serious XSS vulnerability there.

If you're using this in your site as it stands, you are opening up XSS attacks as it does not appear to sanitise user input.

That's a XSS then :)

> If you escape it then there's no XSS issue.

Not XSS, but you need to be careful about allowing through things like the LTR/RTL override characters.


Is it just me or is the first example on their front page a great example of XSS? Unless their standard string formatting routines are performing escaping, this is pretty awful.

Seems like there are some XSS vulnerabilities :D

You need to escape user input to avoid XSS on the page.

Improper input sanitation, you can potentially add raw html to other people's pages (XSS).

Not XSS. I will disclose more once it is fixed.

Those all look like XSS vulnerabilities to me.

Looks like someone has found an XSS attack :D

XSS is a malicious version of the more general problem of not escaping user inputs. its much easier to escape on output rather than input as you can't really tell what's "acceptable". It's also more robust as out of band updates (say direct database updates of comments) get outputted correctly too.

If I have a comment forum with input filtering (rather than output escapong) I can't restrict it to just letters numbers and punctuation or the user's can't discuss HTML tags!


I think misguided XSS protection is the most likely culprit here.

The site is vulnerable to xss

This is the 0% case. No escaping and therefore not safe w.r.t. XSS attacks.

Funny how you can see all the xss attack attempts.

Also, I wonder why some people get a gif.


Indeed, and you'll see they don't filter the input so XSS attacks are possible.

Just enter a question of "<script>foo</script>", and reload the main index to see it happen.


you dont always control your html due to XSS and CSRF.
next

Legal | privacy