# CVE-2025-52352: Missing authorization in n/a

> Attackers can bypass sign-up restrictions via API to create unauthorized admin accounts, gaining full access to the IoT management platform.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2025
- **Updated:** 21 Aug 2025
- **Also known as:** GHSA-7gpf-ch67-224g

## What is CVE-2025-52352?

CVE-2025-52352 is a critical missing authorization vulnerability in n/a, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Aikaan 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-52352?


## How do I fix CVE-2025-52352?

No fix has been published for CVE-2025-52352 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52352 being exploited?

There is no known exploitation of CVE-2025-52352 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52352 and fix it if it is affected.

What it is: CVE-2025-52352 is a critical missing authorization vulnerability in n/a, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52352 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52352/ (Markdown: https://insights.sbomify.com/CVE-2025-52352/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52352
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52352
- OSV: https://osv.dev/vulnerability/CVE-2025-52352

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52352/
Summaries are generated and may contain mistakes; the official description above is the record.