Corporate Credentials Exposed in Public Breach Data
Usernames and passwords for the organisation's email addresses appear in publicly available breach data, and may still work on its services.
| Severity | Medium |
| CVSS 3.1 | 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-308: Use of Single-factor Authentication |
| OWASP Top 10 | A07:2025 Authentication Failures |
| MITRE ATT&CK | T1589.001 Credentials, T1110.004 Credential Stuffing, T1078 Valid Accounts |
| Category | Information Disclosure |
Description
Searches of publicly available breach data found credentials associated with the organisation's email domains: email addresses together with passwords, either in cleartext or as hashes that can be cracked. They typically come from breaches of third-party websites where staff registered with their work address, and increasingly from logs collected by information-stealing malware on personal or work devices, which can also capture session cookies.
The exposure matters because people reuse passwords, or change them predictably, for example by incrementing a number or a year. An attacker can try exposed passwords and their obvious variations against the organisation's internet-facing services, such as Microsoft 365, VPN gateways, remote desktop gateways and webmail, in credential stuffing and password spraying attacks. Where one is still valid and the service does not require a second factor, the attacker can sign in as the user from anywhere, with access to their email and files and possibly remote access to the network, so services that accept a password alone, including legacy protocols that cannot use multi-factor authentication, are most at risk.
The finding is identified by searching breach data sources for the organisation's domains and, where agreed in scope, checking whether exposed credentials or close variants are still accepted. Many exposed passwords are old or no longer valid, and multi-factor authentication blocks their use where it is enforced, which is why the typical case is rated medium; confirmed valid credentials justify a higher rating. Even passwords no longer in use can reveal the patterns users follow when choosing new ones.
Remediation
Make exposed passwords useless, and keep watching for new exposures:
- Enforce multi-factor authentication, preferably phishing-resistant, on every internet-facing service, and block legacy authentication protocols that cannot use it.
- Force a password change for accounts whose exposed credentials may still be in use, and review their sign-in logs for unexpected activity.
- Check new and changed passwords against lists of known breached passwords and common patterns, for example with Microsoft Entra Password Protection and a custom banned password list, and enable leaked credential detection where the identity platform offers it.
- Ask staff not to use work email addresses or passwords for personal services, and provide a password manager so that unique passwords are practical.
- Monitor breach data sources for the organisation's domains, and act on new exposures promptly.
- Apply sign-in protections such as smart lockout, and alert on password spraying.
Confirm the fix by checking that exposed credentials are no longer accepted, and that MFA is enforced on all external services.
References
- cheatsheetseries.owasp.org/cheatsheets/Credential_Stuffing_Prevention_Cheat_Sheet.html
- learn.microsoft.com/en-us/entra/identity/authentication/concept-password-ban-bad
- learn.microsoft.com/en-us/entra/identity/conditional-access/policy-block-legacy-authentication
- owasp.org/Top10/2025/A07_2025-Authentication_Failures
- attack.mitre.org/techniques/T1110/004
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.