I'd suggest closing as a won't fix. The entire point of a random byte generator is to generate a random series of bits of data, and the UserHelper::genRandomPassword() method converts that from a machine collection of data to a human parsable string. Something like bin2hex(random_bytes($length)) (which is a much simpler implementation of that method, but lacking in character range as bin2hex() doesn't give uppercase characters) does have a chance of occasionally putting 3 or 4 characters together that might equate to profanity or otherwise not family friendly words in any Latin character based language, but I would suggest the odds of this happening are so low that adding an offensive term check to anything that's generating random strings adds more overhead to the code without adding cognitive benefit.

Set to "closed" on behalf of @alikon by The JTracker Application at issues.joomla.org/joomla-cms/26526

as pointend above, very low probability that this happens