CVE-2025-52352
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAikaan IoT management platform v3.25.0325-5-g2e9c59796 provides a configuration to disable user sign-up in distributed deployments by hiding the sign-up option on the login page UI. However, the sign-up API endpoint remains publicly accessible and functional, allowing unauthenticated users to register accounts via APIs even when the feature is disabled. This leads to authentication bypass and unauthorized access to admin portals, violating intended access controls.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Aikaan IoT management platform v3.25.0325-5-g2e9c59796 has a access control bypass where disabling user sign-up only hides the UI option on the login page, but the underlying registration API endpoint remains publicly accessible and functional. Unauthenticated attackers can directly invoke the sign-up API to create new accounts, bypassing the intended access restriction and gaining unauthorized access to the platform.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Aikaan versionRun 'aikaan --version' from command line or check the About/Version page in the web UI to confirm the exact version numberAffected if Version matches v3.25.0325-5-g2e9c59796 or falls within the same release line (v3.25.x) where this vulnerability was introduced
-
Verify sign-up is disabled in the UINavigate to the login page of the Aikaan platform and inspect whether the sign-up/register link or button is hidden, removed, or explicitly disabledAffected if The sign-up option appears disabled or hidden in the UI (this is the misleading condition the CVE exploits)
-
Test registration API endpoint directlySend a POST request to the registration API endpoint (typically /api/register, /api/signup, or /api/users/create) with a test email and password payload. For example: curl -X POST https://your-aikaan-host/api/register -d '{"email":"[email protected]","password":"TestPass123"}' -H 'Content-Type: application/json'Affected if The API accepts the request and returns a success or account-created response (HTTP 200/201) even when sign-up appears disabled in the UI, indicating the API is still publicly accessible
If you can successfully create a new account by calling the registration API directly while the sign-up option is hidden or disabled in the UI, your environment is affected by CVE-2025-52352.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable the sign-up API endpoint server-side when the configuration is set, not just hide the UI. Implement proper authorization checks at the API layer to enforce the registration-disabled setting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52352 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data