Sha512 is not a security flaw by itself. You could build an acceptable algorithm with it in Wappler. But do you know how to do that? How are you going to select the salt? Is it secure enough? How will you know?
SHA family of functions were never intended to be used as a means to storing password hashes. They were intended for “digests”. To sign things in other words.
You can use a SHA function as a building block for a secure algorithm(i.e. PBKDF2-HMAC)
But on it’s own your application will be less secure than other apps using a key derivation function.
NIST doesn’t recommend using SHA functions to store “secrets”. They recommend Key Derivation Functions which SHA family are not.
Memorized secrets SHALL be salted and hashed using a suitable one-way key derivation function. Key derivation functions take a password, a salt, and a cost factor as inputs then generate a password hash. Their purpose is to make each password guessing trial by an attacker who has obtained a password hash file expensive and therefore the cost of a guessing attack high or prohibitive. Examples of suitable key derivation functions include Password-based Key Derivation Function 2 (PBKDF2) [SP 800-132] and Balloon [BALLOON].
Argon2, scrypt, bcrypt and old but standardized PBKDF2 are still way better than using any SHA function.
