Anyone using Cisco could be breached by someone logging in with the default passwords Cisco keeps adding (and removing when discovered).
These are basic stuff, a newbie IT should know these things.
I will also assume that (large) organizations test the updates, and have an action plan in place (i.e. apply fix/patch/update XYZ, study what it does, read the documentation, make the future-state-config, deploy that config, validate the config). I know, simple words, we 'all' (in the profession) know this but when you need to patch x1000, and the boss is barking.......
Therefore auditors will look and find nothing, but the accounts are buried there within the system if you know about them (i.e. by exploring a firmware dump and finding the password hash and reversing it).
If these are documented (e.g. IBM has these notorious RedBooks of 500-700-1000 pages) then one should spend the time to study before implementing, securing, auditing, and-other-verbs.
Again, the only 'excuse' I can accept (not really) is that "management" knows that the staff is not enough and they cut corners.. in which case you crucify the COO in your report, not the poor admin(s).
Even if they want to use them for ML, this shouldn't be reason to reduce the perceived sensitivity of the data to let them sit on an online device, as the harm hasn't reduced. Hopefully we'll see more threat models based on the impact of harm, not on the convenience to business.