Exposed Salesforce logins and password spraying
The short version: A Salesforce login exposed to the internet lets attackers quietly spray common and already-breached passwords across your accounts until one works — no exploit required, just an exposed login and one weak credential.
What you need to know
There's no CVE here and nothing to patch. The weakness is the combination of exposure and weak authentication: a login an attacker can reach, in front of accounts whose passwords may be guessable, reused from another site, or already sitting in a public breach dump.
Password spraying is the technique that turns that combination into access. Rather than guess many passwords against one account (which trips lockouts), an attacker tries a few high-probability passwords against many accounts, slowly and quietly.
- How they find it — routine internet-wide scanning and reconnaissance surface your Salesforce login surface.
- How they use it — automated, low-and-slow spraying with common and previously-breached passwords, staying under lockout thresholds.
- What it leads to — a working credential reaches your CRM: customer records, contracts, pipeline, and often connected apps and integrations. That's sensitive business data and a springboard into whatever the account is authorized to touch.
How serious we see it
Low — by default, with honest upside risk. An exposed login protected by strong, unique credentials and enforced MFA is a manageable exposure, not an emergency, which is why we don't cry "Critical" on sight. But the real severity depends on what's behind the door: if any account uses a weak or reused password and MFA isn't enforced, this quietly becomes High — a direct, unauthenticated path to customer data. The reassuring part is that it's entirely in your hands to fix, with no vendor patch required.
What to do
- Enforce MFA on every Salesforce user — the single highest-value control; it defeats spraying even when a password is known. Salesforce requires MFA for direct logins, so confirm it's active and not bypassed via legacy paths.
- Restrict access where you can — use trusted IP ranges and login-hour policies to shrink the exposed surface.
- Limit and monitor failed authentication — alert on spray patterns (many accounts, few passwords, low-and-slow).
- Kill weak and reused passwords — enforce strong, unique credentials and check them against known-breached lists.
- Confirm your exposure first — verify how your Salesforce login is reachable and which accounts lack MFA.
How BreachRisk sees it
BreachRisk discovers Salesforce login portals exposed to the internet the way an attacker would — by crawling your external footprint — and then, where authorized, goes a step further than a scanner: it safely attempts a bounded, rate-limited authentication check using exposed (breach-corpus) and common credentials, within strict non-disruptive limits rather than a brute-force flood. That's the honest difference between detecting a login and demonstrating whether it actually holds. "We have a Salesforce login on the internet" becomes a straight answer: is it defended, or one reused password away from access?