In a UX-focused discussion titled “Interface issue resulting in revealing passwords,” yaxu reports that five users accidentally entered their passwords into a newly added “pronouns” profile field, mistaking it for a password confirmation field. The issue arose because the field’s placement and label resembled typical password entry forms. yaxu is wiping the affected entries and notifying users of the potential breach. seanblue questions whether users didn’t notice their passwords were in plaintext, to which yaxu replies that the forum’s users—live coders—are fast typists and likely didn’t catch the mistake. Suggestions for fixes include renaming the field to avoid confusion with “P”-prefixed fields like “Password” Canapin, adding visual dividers or CSS separators, or converting the field into a dropdown with predefined options. yaxu plans to implement these changes and monitor the results, suggesting that placing the password field last might be the best general solution. maiki recommends rewording the label to something like “I like to be called…” or “You may refer to me by…” to make its purpose clearer while retaining helpful descriptive text. The thread highlights how subtle UI design choices can lead to serious security oversights, even among technically adept users.
However maybe you already see the issue - people are used to giving their password twice on such forms.. and five people already did exactly that, putting their password in the ‘pronouns’ field! I’m now in the process of wiping this field for those affected and notifying them of the potential breach..
I’m not sure what interface tweaks would get around this problem. Maybe putting the password field last, or putting a divider around it? I’m going to try renaming the field so it looks less like “Password”..
As you said, I’d rename the field to something less similar than “P[something]” and separate it from the mandatory fields with a bit of css (adding an horizontal line or something like that).
Or maybe make the field a list with predefined choices so people won’t use the field for something else.