Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public signup API unauthenticated
-
DeliveryCraft signup with multi-address email field
-
ExploitService sends OTP to all recipients
-
ExecutionCapture OTP at attacker address
-
ImpactComplete registration impersonating victim email
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Anti-spoofing controls
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target expose the Frappe Cloud/ERPNext self-service registration endpoint /api/method/press.api.account.signup to the attacker (the default for Frappe Cloud's public signup and any ERPNext deployment with open registration). The concrete prerequisite is the ability to submit a signup request whose email field contains more than one address, at least one of which is valid/attacker-controlled; the server then processes the entire value as a recipient list. No authentication, user interaction, or non-default configuration is needed (PR:N/UI:N). The primary LIMITING factor is deployment exposure: installations that disable open/self-service signup, restrict registration to invited or SSO users, or front the endpoint with validation/WAF controls are not reachable, and impact is bounded to the registration/OTP flow rather than existing account compromise. |
| Impact | This is a moderate-severity authentication-design flaw (CWE-290) rated 6.9 via CVSS 4.0 (AV:N/AC:L/AT:N/PR:N/UI:N) with only Low confidentiality and Low integrity impact (VC:L/VI:L) and no availability impact. The vector signals favor exploitation - network-reachable, low complexity, no authentication, no user interaction - meaning any remote attacker can hit the /api/method/press.api.account.signup endpoint directly. However, the real-world severity is tempered by the limited impact: the flaw enables OTP interception for the signup/registration flow and email-existence enumeration, not direct takeover of existing provisioned accounts or data exfiltration. No EPSS score, KEV listing, or POC indicator was supplied in the input, so exploitation likelihood cannot be quantified from probabilistic signals and there is no public exploit identified at time of analysis. The CVSS vector (unauthenticated network) is internally consistent with the description ('unauthenticated remote attacker'), so there is no AV conflict to flag. Net assessment: a legitimate account-integrity/impersonation issue worth patching on exposed Frappe Cloud/ERPNext signup surfaces, but not an emergency 'drop everything' flaw absent evidence of active exploitation - treat as medium priority weighted by how exposed the registration endpoint is. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a signup request to /api/method/press.api.account.signup with the email field manipulated to contain multiple addresses (e.g. the victim's real address plus an attacker-controlled one), where only one needs to be valid. The service treats the whole value as a recipient list and delivers the OTP to all addresses, letting the attacker capture the code and complete registration while impersonating the victim's email, or confirm whether a given email is already registered. No public exploit is identified at time of analysis, and the low attack complexity (AC:L) means the crafted request requires no special timing or preconditions. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Frappe Cloud and ERPNext fail to properly validate the email field in the self-service registration endpoint /api/method/press.api.account.signup, allowing unauthenticated remote attackers to supply multiple email addresses and have the OTP code delivered to all of them as long as one address is valid. This can lead to OTP interception, impersonation during registration, creation of accounts using other people's email addresses without mailbox access, and indirect confirmation of already registered emails. The issue is rated moderate (CVSS 4.0 6.9, CVSS 3.1 6.9 with low confidentiality and integrity impact); no public exploit identified at time of analysis, and impact is limited to deployments that expose open self-service signup.
RemediationAI
No vendor-released patch identified at time of analysis. Until a fix is available, administrators should disable open/self-service registration and restrict account creation to invited or SSO-authenticated users; this directly removes the attack surface but may break legitimate self-service onboarding. Alternatively, place the endpoint /api/method/press.api.account.signup behind a WAF or reverse proxy that rejects requests where the email field contains more than one address (e.g., by allowing only a single RFC 5322 address, with no commas or whitespace-separated lists) - a compensating control that could affect users who legitimately need aliases. Rate limiting or blocking unauthenticated POSTs to the endpoint, and monitoring for OTPs sent to multiple addresses, can reduce exploitation attempts. Consult the INCIBE advisory at https://www.incibe.es/en/incibe-cert/notices/aviso/authentication-bypass-multiple-products-frappe-technologies for updates and any vendor-provided mitigation guidance.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is an authentication bypass by spoofing (CWE-290) in Frappe Technologies products, specifically Frappe Cloud's signup API and ERPNext deployments that use the same registration flow. The endpoint /api/method/press.api.account.signup accepts a single email field, but the server processes the entire value as a comma- or space-separated recipient list and sends the one-time password (OTP) to every address without validating that all belong to the requester; only one address needs to be valid for the OTP to be delivered. Per the independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), no authentication or user interaction is required, and the primary limiting factor is deployment exposure - installations that disable open registration, restrict signups to invited or SSO users, or front the endpoint with validation/WAF controls are not reachable. Impact is bounded to the registration/OTP flow rather than compromise of existing accounts.
Know when Frappe Technologies gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Unauthenticated network-reachable signup endpoint (AV:N/AC:L/PR:N/UI:N); OTP interception and email enumeration give limited confidentiality and impersonation/integrity impact (C:L/I:L), no availability effect, scope unchanged.
Primary rating from Vendor (INCIBE).
CVSS VectorVendor: INCIBE
DescriptionCVE.org
A vulnerability has been identified regarding insufficient validation in the Frappe Cloud/ERPNext authentication process, which allows multiple email addresses to be accepted by manipulating the email field in the /api/method/press.api.account.signup endpoint. The vulnerability occurs when an unauthenticated remote attacker adds more than one email address. The service processes the entire value as a valid list of recipients and sends the OTP code to all addresses without proper validation of all added emails (only one of them needs to be valid). Exploiting this vulnerability would allow an attacker to:
- Obtain the authentication OTP;
- Impersonate someone else in the registration process;
- Register accounts using other people's email addresses without access to the mailbox;
- Indirectly confirm the existence of already registered email addresses.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-94811
GHSA-44qm-r6v9-65h7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB