Funny story...
Did some work for a company using their development environment. We had a BA enter accounts to run test cases. He set up about a dozen but one was odd because the rest were like TestAccount1, TestAccount2, etc... Turned out to be the name of an actual ex Jenny _______ with the password = hotsex69.
He didn't know that column encryption wasn't enabled on the password field in the user table because it was a dev environment.
For the remainder of my time there, I called him Hotsex. He had a good sense of humor![]()
Another story...
Did some work for a different company with an online presence where I was a customer many years ago. They replicated their production DB into a dev/test environment and failed to anonymize the PII and remove the passwords. There was my name, SSN, address, and password from many years prior.
Last one...
Had a coworker need help with login, called the helpdesk and had them on speakerphone. Rep asked for his password. This was an ancient AS/400 system that limited us to four characters. His password? POOP. Rep says "what?" He responds "PEE OOH OOH PEE." We died.
Moral of the story: Just because the UI doesn't show your password doesn't mean other people can't see it.
Side note: It is incredibly easy to anonymize info and obliterate passwords in data. Whenever I move data, I make it a point to do this. Even financial data for companies is scrubbed. But don't you dare tell a DBA why that's important because they know best even when they don't.