Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Welcome to the community. If I understand correctly the first question is simply manipulation within the frontend, which is normal (please correct me if I'm wrong) Commented Aug 6, 2024 at 9:39
  • 2
    while frontend validations are nice to have, they do not replace the need for backend validations. (So for number of characters, make backend validate that as well and respond back when it fails... same goes for any disallowed characters.) Commented Aug 6, 2024 at 20:03
  • Welcome! I edited your question adding a few backticks to make the actual code visible (as Stack Exchange is doing some filtering to avoid these kinds of vulnerabilities). Feel free to edit again. Commented Aug 6, 2024 at 23:35
  • @Sir Muffington Thank you, it's great to be here. You are correct; the issue is indeed related to frontend manipulation. My concern is that users can insert very long strings, payloads, or other potentially harmful input into the input field, which will be stored in the database. Commented Aug 7, 2024 at 6:54
  • @browsermator Thank you for the advice. I'll be doing some research on how to properly implement these validations. Commented Aug 7, 2024 at 6:58