I don't see what the problem is here 
From what I see "test1%40test.com" % has stopped the @ symbol this does not mean a wallet is insecure they have their own means of password hashing
Code:
user_name=815ff46a-d01a-4582-ace7-9357a066c32d&email=test1%40test.com&password=test1234%21&password_repeat=test1234%21®ister=REGISTER
From what I see "test1%40test.com" % has stopped the @ symbol this does not mean a wallet is insecure they have their own means of password hashing
That's not what i am talking about.
That's what i am talking about:
user_name=815ff46a-d01a-4582-ace7-9357a066c32d&email=test1%40test.com&password=test1234%21&password_repeat=test1234%21®ister=REGISTER
You don't transmit the plain text password to store it in the DB.
Usually you hash it client-side and transmit the hash, which then is stored in the DB.
Quote from: https://www.sendbit.io/page/our_security
Application
We use SQL injection filters to prevent CSRF attacks and XSS attacks [...]
This doesn't make sense at all.
What doesn't make sense about this? It makes total sense to me... We use SQL injection filters to prevent CSRF attacks and XSS attacks [...]
This doesn't make sense at all.
CSRF has absolutely nothing to do with SQL injection.
You can NOT prevent CSRF with any SQL filter.
If THIS is making sense to you, then you obviously don't have a clue about those attack vectors.
you can see my merits
Is this a joke ?