Unauthenticated account creation via missing verification enforcement
Published Dec 30, 2025 · Updated Dec 30, 2025
Improper authentication in Zeroheight before 2025-06-13 allows remote attackers to create accounts through a legacy sign-up API. The legacy pathway processed new registrations without requiring a valid email-verification token or enforcing the intended verification check. The unauthenticated flow creates unverified accounts that cannot use product features, limiting impact to fake-account flooding and resource consumption; no existing-account access or data exposure was reported.
Summary
What happened
Improper authentication in Zeroheight before 2025-06-13 allows remote attackers to create accounts through a legacy sign-up API. The legacy pathway processed new registrations without requiring a valid email-verification token or enforcing the intended verification check. The unauthenticated flow creates unverified accounts that cannot use product features, limiting impact to fake-account flooding and resource consumption; no existing-account access or data exposure was reported.
The record
- CVE
- CVE-2025-65925
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287, T1136.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo