3

Is obtaining the value of a textarea/input with the jQuery function .val() XSS-proof?

<html>
    <textarea id="t1"></textarea>
    <script> 
        var toBeDisplayed = $('#t1').val();
        $('#elem').html(toBeDisplayed);
    </script>
</html>
  • 2
    You don’t have to care for where the value comes from ($('#t1').val()) but where it goes to ($('#elem').html()). – Gumbo Feb 28 '14 at 13:38
5

As Gumbo mentioned in his comment, it does not matter what you read in, but it does matter what you display after the fact. To simply answer your question, no. jQuery's .val() does not have any filtering that will protect you from XSS. You could perhaps take in the value into var toBeDisplayed and then perform your own filtering before it gets relayed to be displayed again.

  • 1
    What if I assign toBeDisplayed to another textarea using jQuery.val(), example: $('#another-textarea').val(toBeDisplayed);, Should I worry about XSS? – tonix Aug 3 '16 at 16:59
  • 1
    Can someone explain further? It seems to me that JQuery is simply using a direct value attribute assignment via the JS DOM API. What attacks are possible in this case? See also this SO article: security.stackexchange.com/questions/139749/… – Eric Nguyen Sep 11 '17 at 23:13
  • @EricNguyen - as far as I know, you are correct, and val() can't cause XSS under any conditions as it doesn't concatenate strings or any such, it creates DOM nodes through API. That would mean that this answer is 100% wrong. – Davor Jan 16 '18 at 13:04
0

Of course it is always safest to do the sanitizing on the server side before displaying the input back to the user. It can be done more quickly and easily in the browser, but any code running in the browser should not be considered entirety trusted; it could be modified or disabled.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.