Summary
A user enumeration flaw in the docuForm FSM Client login interface leaks information about which usernames are valid through differing server responses.
Remote attackers can use these subtle response variations to discover existing accounts, enabling targeted brute-force and credential stuffing attacks against identified users.
Affected context
This vulnerability occurs in deployments of the docuForm GmbH FSM Client that expose the login.php authentication endpoint over a network.
It manifests when the login mechanism produces observably different responses—such as messages, status codes, or timing—for valid versus invalid usernames.
The issue is most relevant in environments where attackers can freely interact with the login form and repeatedly submit authentication attempts.
Exploit preconditions
- Attack surface: Public or internal web login interface (
login.php) reachable over HTTP/HTTPS - Required access: Ability to send unauthenticated login requests and observe server responses
- Trigger point: Submission of crafted usernames to the login endpoint during authentication attempts
- Why exploitation is possible: The authentication logic reveals differences in error messaging or behavior between existing and non-existing accounts, creating an oracle for username validity
Why this happens
The underlying bug aligns with CWE-203: Information Exposure Through Discrepancy, where a system unintentionally discloses sensitive state based on varying responses.
In this case, the authentication component treats username existence as part of the observable output, returning distinct messages, codes, or timing characteristics for valid versus invalid usernames.
This pattern violates the principle of uniform error handling in authentication flows, allowing attackers to infer account presence without proper authorization.
Potential impact
- Attackers may map out lists of valid usernames for the FSM Client system.
- Discovered accounts could be targeted with brute-force password guessing.
- Credential stuffing attacks can be focused on known valid usernames.
- Increased risk of account takeover for users with reused or weak passwords.
- Enhanced reconnaissance that aids further social engineering or phishing campaigns.
General mitigation guidance
Effective mitigation generally focuses on normalizing authentication responses and reducing observable differences in login behavior.
Recommended defensive patterns include:
- Returning generic error messages that do not distinguish between invalid username and incorrect password.
- Ensuring similar HTTP status codes, response bodies, and timing for all failed authentication attempts.
- Applying rate limiting and progressive delays on repeated login failures to reduce automated enumeration.
- Implementing multi-factor authentication to limit the impact of credential-based attacks.
- Designing authentication workflows so that account existence is never confirmed to unauthenticated clients.
How teams detect issues like this
Detection often involves analyzing authentication flows for response discrepancies tied to account validity.
Common strategies include:
- Reviewing login code paths to ensure uniform error handling for all failed attempts.
- Performing security testing that compares responses for valid and invalid usernames (messages, codes, timing).
- Using static analysis or linting rules that flag conditional logic producing distinct outputs based on username existence.
- Enforcing security design reviews for authentication components with a focus on information exposure and consistency.

