CVE-2026-50635: LimeSurvey Password Reset Host Header Injection Discloses Reset Token
LimeSurvey constructs account password-reset links from the client-supplied HTTP Host header without validating it. The optional allowedHosts allowlist that would constrain this is undefined in the default (and documented) configuration, so LSHttpRequest::checkIsAllowedHost() results in no operation. A remote, unauthenticated attacker who submits a forgotten-password request for a known account (requiring only the target's username and email) with a spoofed Host header causes LimeSurvey to email that account a reset link whose hostname is attacker-controlled while embedding the genuine validationkey. When the recipient or an automated inbound mail-security link scanner dereferences the link, the valid reset token is disclosed to the attacker, who replays it against the legitimate host's newPassword endpoint to set a new password and take over the account.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Set the allowedHosts configuration to a specific list of legitimate application hostnames so that LSHttpRequest::checkIsAllowedHost() validates the Host header and is not a no-op; this prevents password-reset links from being built using attacker-controlled Host headers.
LimeSurvey (LSHttpRequest::checkIsAllowedHost) allowedHosts = define a non-empty allowlist of permitted host header values (only your legitimate LimeSurvey hostnames)
Event History
Frequently Asked Questions
What is the severity of CVE-2026-50635?
The severity of CVE-2026-50635 is rated as high with a score of 8.7.
How does CVE-2026-50635 affect LimeSurvey?
CVE-2026-50635 allows attackers to exploit the password reset functionality by injecting malicious Host headers, potentially disclosing sensitive reset tokens.
How do I fix CVE-2026-50635?
To fix CVE-2026-50635, configure the allowedHosts allowlist in LimeSurvey's configuration to define and restrict valid hostnames.
What are the potential impacts of CVE-2026-50635?
The potential impacts of CVE-2026-50635 include unauthorized access to user accounts and exposure of sensitive information such as reset tokens.
Is there a workaround for CVE-2026-50635?
A temporary workaround for CVE-2026-50635 is to disable the password reset feature until a proper fix is applied.