VulnerabilityPublished 29 Aug 2025

CVE-2025-39246: Hikvision HikCentral FocSign · CWE-428

Affects Hikvision HikCentral FocSignSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Hikvision HikCentral FocSign	Affected =2.2.0	Fixed in–

AI-suggested

European organizations should take specific steps beyond generic advice: 1) Immediately audit all systems running HikCentral FocSign versions 1.4.0 through 2.2.0 to identify vulnerable installations. 2) Restrict local access to these systems strictly to trusted personnel and enforce strong authentication and access controls to reduce the risk of an attacker gaining authenticated local access. 3) Monitor for any unusual local activity or privilege escalation attempts on these systems using endpoint detection and response (EDR) tools. 4) Implement application whitelisting and restrict execution paths to prevent unauthorized executables from running in directories that could be exploited due to unquoted service paths. 5) Engage with Hikvision or authorized vendors to obtain patches or updates as soon as they become available and plan for timely deployment. 6) Consider deploying host-based hardening measures such as enforcing service path quoting manually or using security tools that detect and remediate unquoted service paths. 7) Conduct user training to raise awareness about the risks of local privilege escalation and the importance of safeguarding credentials and local system access.

Description

There is an Unquoted Service Path Vulnerability in some HikCentral FocSign versions. This could allow an authenticated user to potentially enable escalation of privilege via local access.

Impact

For European organizations, the impact of this vulnerability can be significant, especially for those relying on Hikvision's HikCentral FocSign for managing physical security infrastructure such as access control and visitor management. Privilege escalation on systems running this software could allow attackers to manipulate security configurations, disable security controls, or gain persistent access to sensitive physical security systems. This could lead to unauthorized physical access, data integrity issues, or disruption of security operations. Given the critical role of physical security in sectors like government, transportation, critical infrastructure, and corporate environments, exploitation could have cascading effects on operational security and compliance with regulations such as GDPR. Although the vulnerability requires local authenticated access, insider threats or attackers who have gained initial footholds could leverage this to escalate privileges and move laterally within networks. The absence of known exploits reduces immediate risk but does not preclude targeted attacks, especially in high-value environments.

CWE-428Unquoted Search Path or Element (opens in a new tab)
Base weakness
The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path.
Implementation
Properly quote the full search path before executing a program on the system.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

hikvision.com/en/support/cybersecurity/security-advisory/security-vulnerabilities-in-some-hikcentral-products/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Aug 2025, 02:33 UTC

WeaknessesCWE-428

Technical details

References

Community reviews

Related threats