Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65925: n/a

0
Medium
VulnerabilityCVE-2025-65925cvecve-2025-65925
Published: Tue Dec 30 2025 (12/30/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

An issue was discovered in Zeroheight (SaaS) prior to 2025-06-13. A legacy user creation API pathway allowed accounts to be created without completing the intended email verification step. While unverified accounts could not access product functionality, the behavior bypassed intended verification controls and allowed unintended account creation. This could have enabled spam/fake account creation or resource usage impact. No data exposure or unauthorized access to existing accounts was reported.

AI-Powered Analysis

AILast updated: 01/06/2026, 22:44:17 UTC

Technical Analysis

CVE-2025-65925 identifies a security weakness in Zeroheight, a SaaS platform, discovered prior to June 13, 2025. The vulnerability stems from a legacy user creation API pathway that allowed new accounts to be created without enforcing the intended email verification step. This flaw means that attackers or automated scripts could create multiple unverified accounts bypassing the verification process. Although these unverified accounts do not grant access to the platform's product functionality, the ability to create accounts without verification undermines the platform's authentication controls. This could lead to spam or fake account creation, potentially resulting in resource exhaustion or degraded service performance. Importantly, there is no indication that this vulnerability allows unauthorized access to existing user accounts or exposure of sensitive data. The CVSS v3.1 base score is 6.5 (medium severity), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality impact, low integrity impact, and low availability impact. The vulnerability is categorized under CWE-287, indicating improper authentication mechanisms. No patches or exploits are currently reported, but the issue is publicly disclosed and should be mitigated.

Potential Impact

For European organizations using Zeroheight, this vulnerability could facilitate automated creation of large numbers of unverified accounts, which may be exploited for spam campaigns or to consume platform resources, potentially leading to service degradation or denial of service conditions. While the direct impact on confidentiality and integrity is low, the availability of the service could be affected if resource exhaustion occurs. Additionally, the presence of numerous fake accounts could complicate user management and analytics, impacting operational efficiency. Organizations in sectors with strict compliance requirements may face reputational risks if the platform is abused for malicious activities. Since no unauthorized access to existing accounts or data leakage is reported, the direct risk to sensitive information is minimal. However, the vulnerability could be leveraged as part of a broader attack chain or social engineering campaigns targeting European enterprises.

Mitigation Recommendations

European organizations should immediately review their use of Zeroheight and confirm whether they are running affected versions prior to the June 13, 2025 fix. Since no official patch links are provided, organizations should contact Zeroheight support to obtain or confirm the availability of a fix that enforces email verification on all account creations. In the interim, organizations can implement compensating controls such as monitoring account creation logs for spikes in unverified accounts, rate limiting API calls related to user creation, and deploying CAPTCHA or other bot mitigation techniques on account registration endpoints if configurable. Additionally, integrating Zeroheight with identity providers that enforce strong authentication and verification can reduce reliance on the vulnerable legacy API. Regular audits of user accounts to identify and remove unverified or suspicious accounts will help maintain platform hygiene. Finally, organizations should update incident response plans to include detection and mitigation of abuse stemming from fake account creation.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-11-18T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 695450a4db813ff03e2be15a

Added to database: 12/30/2025, 10:22:28 PM

Last enriched: 1/6/2026, 10:44:17 PM

Last updated: 2/4/2026, 5:57:50 AM

Views: 32

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats