Exposed SAP Fiori logins and password spraying
The short version: An SAP Fiori 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 surfaces exposed SAP Fiori launchpad login pages.
- How they use it — automated, low-and-slow spraying with common and previously-breached passwords, staying under lockout thresholds.
- What it leads to — Fiori is the front door to SAP, and SAP is where finance, HR, supply chain, and other core business processes live. A working credential reaches sensitive data, and depending on the account's roles, the ability to act inside business-critical systems.
How serious we see it
Moderate — by default, but with real upside risk given what SAP guards. 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 path into ERP data and workflows. 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 SAP Fiori account — the single highest-value control; it defeats spraying even when a password is known.
- Get the launchpad off the open internet where you can — front it with a VPN, reverse proxy, or trusted-network restriction.
- Limit and monitor failed authentication — rate-limit attempts and alert on spray patterns (many accounts, few passwords, low-and-slow).
- Kill weak and reused passwords — enforce strong, unique credentials, retire default accounts, and check against known-breached lists.
- Confirm your exposure first — verify whether any SAP Fiori login is reachable from the internet at all.
How BreachRisk sees it
BreachRisk discovers SAP Fiori 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 an SAP login on the internet" becomes a straight answer: is it defended, or one reused password away from access?