# CVE-2025-39247: Auth bypass in HikCentral Professional

> Unauthenticated attackers can bypass access controls to gain admin privileges in HikCentral Professional, requiring immediate patching.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-mx8f-fqhw-v9m2

## What is CVE-2025-39247?

CVE-2025-39247 is a high-severity authentication bypass vulnerability in Hikvision HikCentral Professional, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is an Access Control Vulnerability in some HikCentral Professional versions. This could allow an unauthenticated user to obtain the admin permission.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-39247 being exploited?

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

Public exploit code:

- HikCentral Professional - Pre-Auth License ActiveCode Leak (github_poc): https://github.com/Sita-Technologies/CVE-2025-39247

## Fix prompt for AI coding agents

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

What it is: CVE-2025-39247 is a high-severity authentication bypass vulnerability in Hikvision HikCentral Professional, published on 29 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-39247 in the wild and no public exploit code.

Affected product: Hikvision HikCentral Professional. 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-39247/ (Markdown: https://insights.sbomify.com/CVE-2025-39247/index.md)
```

## Sources

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

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