Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-4894 Overview
CVE-2026-4894 is an authentication bypass vulnerability in the Frappe Cloud and ERPNext signup process. The flaw resides in the /api/method/press.api.account.signup endpoint, which fails to validate that the email field contains only a single address. An unauthenticated remote attacker can submit multiple email addresses in one request, and the service delivers the one-time password (OTP) to all recipients. This weakness is classified as [CWE-290] Authentication Bypass by Spoofing.
Critical Impact
An attacker can intercept OTP codes, register accounts using someone else's email address, impersonate legitimate users during signup, and confirm the existence of registered accounts.
Affected Products
- Frappe Cloud
- Frappe ERPNext
- press.api.account.signup API endpoint
Discovery Timeline
- 2026-10-08 - CVE-2026-4894 published to the National Vulnerability Database (NVD)
- 2026-10-08 - Last updated in NVD database
Technical Details for CVE-2026-4894
Vulnerability Analysis
The signup endpoint /api/method/press.api.account.signup accepts user-supplied input in the email field without enforcing that the value contains a single, well-formed address. When an attacker submits a value containing multiple comma-separated addresses, the backend parses the entire string as a recipient list rather than rejecting it as invalid input. The OTP generated for the registration attempt is then delivered to every address in the list.
Because only one of the supplied addresses needs to be valid and controlled by the attacker, the attacker can direct the OTP to their own inbox while associating the registration with a victim's email. This defeats the proof-of-ownership guarantee the OTP flow is designed to provide. The vulnerability also enables account enumeration, because responses differ when one of the supplied addresses is already registered.
Root Cause
The root cause is insufficient input validation on the email parameter in the signup handler. The application treats the field as a mail-recipient list and passes it to the mail dispatch layer without constraining it to a single RFC 5322 address. No normalization or sanitization rejects comma-delimited, semicolon-delimited, or header-injection style inputs.
Attack Vector
Exploitation requires no authentication and no user interaction. The attacker sends a single HTTP POST request to the signup endpoint over the network, embedding both an attacker-controlled address and a victim address in the email field. The attacker receives the OTP, completes the registration workflow, and binds the account to the victim's identity. See the INCIBE Security Notice for additional vendor-provided details.
No verified exploit code is published. The vulnerability mechanism
is described in prose above and in the INCIBE advisory linked in
the External References.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-4894
Indicators of Compromise
- POST requests to /api/method/press.api.account.signup containing commas, semicolons, or multiple @ symbols within the email parameter.
- OTP emails delivered to multiple distinct recipients for a single signup transaction.
- Account registrations where the registered email differs from the inbox that received the OTP confirmation.
Detection Strategies
- Parse application and web-server logs for signup requests whose email field fails strict single-address validation.
- Correlate mail-gateway logs with signup events to identify OTP messages fanned out to multiple recipients.
- Alert on bursts of signup attempts from a single source IP targeting the press.api.account.signup endpoint.
Monitoring Recommendations
- Enable verbose logging on the Frappe press API and retain request bodies for the signup endpoint.
- Monitor outbound SMTP traffic for OTP templates addressed to more than one recipient per transaction.
- Track account creation metrics and flag accounts whose owning email domain does not match the OTP delivery destination.
How to Mitigate CVE-2026-4894
Immediate Actions Required
- Apply vendor updates for Frappe Cloud and ERPNext as soon as they are available from Frappe Technologies.
- Deploy a WAF rule that rejects signup requests whose email parameter contains commas, semicolons, or more than one @ character.
- Review recent account registrations for signs of exploitation and disable suspicious accounts pending verification.
Patch Information
Refer to the INCIBE Security Notice for the current list of vendor-fixed versions. Administrators should subscribe to Frappe Technologies security announcements and apply updates to both self-hosted and managed ERPNext deployments.
Workarounds
- Place the press.api.account.signup endpoint behind an API gateway that enforces a strict single-address regex on the email field before forwarding the request.
- Rate-limit signup attempts per source IP to slow enumeration and bulk abuse.
- Add server-side validation that rejects any OTP dispatch targeting more than one recipient address.
# Example NGINX rule to reject multi-address signup payloads
location /api/method/press.api.account.signup {
if ($request_body ~* "\"email\"\s*:\s*\"[^\"]*[,;][^\"]*\"") {
return 400;
}
proxy_pass http://frappe_backend;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

