An Improper Authentication issue was discovered in Hikvision DS-2CD2xx2F-I Series V5.2.0 build 140721 to V5.4.0 build 160530, DS-2CD2xx0F-I Series V5.2.0 build 140721 to V5.4.0 Build 160401, DS-2CD2xx2FWD Series V5.3.1 build 150410 to V5.4.4 Build 161125, DS-2CD4x2xFWD Series V5.2.0 build 140721 to V5.4.0 Build 160414, DS-2CD4xx5 Series V5.2.0 build 140721 to V5.4.0 Build 160421, DS-2DFx Series V5.2.0 build 140805 to V5.4.5 Build 160928, and DS-2CD63xx Series V5.0.9 build 140305 to V5.3.5 Build 160106 devices. The improper authentication vulnerability occurs when an application does not adequately or correctly authenticate users. This may allow a malicious user to escalate his or her privileges on the system and gain access to sensitive information.
CVE-2017-7921
Score elevated to 10.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-03-05), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 10.0(high)
- EG Risk
- 100(Act)EG Risk 100/100SSVC: Act
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity100% × 45%Exploitation100% × 40%Automatability100% × 15%Action: Fix now — active exploitation, automatable, high impact. - EPSS PROB
- 100%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
May 6, 2017
Last Modified
June 17, 2026
Advisory Details (5)
Auto-updated Sep 14, 2026Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 49× in last 7d / 206× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 785 total refreshes for this CVE.
- 2026-09-20 19:11 UTCGHSA enrichment
- 2026-09-20 15:25 UTCGHSA enrichment
- 2026-09-20 11:39 UTCGHSA enrichment
- 2026-09-20 07:52 UTCGHSA enrichment
- 2026-09-20 04:03 UTCGHSA enrichment
- 2026-09-20 00:17 UTCGHSA enrichment
- 2026-09-19 20:31 UTCGHSA enrichment
- 2026-09-19 16:45 UTCGHSA enrichment
- 2026-09-19 12:59 UTCGHSA enrichment
- 2026-09-19 09:13 UTCGHSA enrichment
- 2026-09-19 05:27 UTCGHSA enrichment
- 2026-09-19 01:41 UTCGHSA enrichment
- 2026-09-18 21:55 UTCGHSA enrichment
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 18:10 UTCGHSA enrichment
- 2026-09-18 14:24 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 10:38 UTCGHSA enrichment
- 2026-09-18 06:51 UTCGHSA enrichment
- 2026-09-18 03:05 UTCGHSA enrichment
- 2026-09-17 23:19 UTCGHSA enrichment
- 2026-09-17 19:33 UTCGHSA enrichment
- 2026-09-17 15:47 UTCGHSA enrichment
- 2026-09-17 12:01 UTCGHSA enrichment
- 2026-09-17 08:15 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-17 04:29 UTCGHSA enrichment
- 2026-09-17 00:43 UTCGHSA enrichment
- 2026-09-16 20:56 UTCGHSA enrichment
- 2026-09-16 16:57 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 13:10 UTCGHSA enrichment
- 2026-09-16 09:24 UTCGHSA enrichment
- 2026-09-16 05:37 UTCGHSA enrichment
- 2026-09-16 01:52 UTCGHSA enrichment
- 2026-09-15 22:06 UTCGHSA enrichment
- 2026-09-15 18:20 UTCGHSA enrichment
- 2026-09-15 14:34 UTCGHSA enrichment
- 2026-09-15 10:47 UTCGHSA enrichment
- 2026-09-15 07:00 UTCGHSA enrichment
- 2026-09-15 03:14 UTCGHSA enrichment
- 2026-09-14 23:28 UTCGHSA enrichment
- 2026-09-14 19:42 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 15:56 UTCGHSA enrichment
- 2026-09-14 12:10 UTCGHSA enrichment
- 2026-09-14 08:23 UTCGHSA enrichment
- 2026-09-14 04:37 UTCGHSA enrichment
- 2026-09-14 00:52 UTCGHSA enrichment
- 2026-09-13 21:06 UTCGHSA enrichment
- 2026-09-13 17:20 UTCGHSA enrichment
- 2026-09-13 13:34 UTCGHSA enrichment
- 2026-09-13 09:47 UTCGHSA enrichment
- 2026-09-13 06:02 UTCGHSA enrichment
- 2026-09-13 02:16 UTCGHSA enrichment
- 2026-09-12 22:30 UTCGHSA enrichment
- 2026-09-12 18:44 UTCGHSA enrichment
- 2026-09-12 14:58 UTCGHSA enrichment
- 2026-09-12 11:12 UTCGHSA enrichment
- 2026-09-12 07:26 UTCGHSA enrichment
- 2026-09-12 03:40 UTCGHSA enrichment
- 2026-09-11 23:54 UTCGHSA enrichment
- 2026-09-11 20:08 UTCGHSA enrichment
- 2026-09-11 18:49 UTCCISA KEV update
- 2026-09-11 16:22 UTCGHSA enrichment
- 2026-09-11 12:35 UTCGHSA enrichment
- 2026-09-11 08:47 UTCGHSA enrichment
- 2026-09-11 05:01 UTCGHSA enrichment
- 2026-09-11 01:15 UTCGHSA enrichment
- 2026-09-10 21:29 UTCGHSA enrichment
- 2026-09-10 19:28 UTCCISA KEV update
- 2026-09-10 17:43 UTCGHSA enrichment
- 2026-09-10 13:57 UTCGHSA enrichment
- 2026-09-10 10:11 UTCGHSA enrichment
- 2026-09-10 06:25 UTCGHSA enrichment
- 2026-09-10 02:39 UTCGHSA enrichment
- 2026-09-09 22:53 UTCGHSA enrichment
- 2026-09-09 19:08 UTCCISA KEV update
- 2026-09-09 19:07 UTCGHSA enrichment
- 2026-09-09 15:21 UTCGHSA enrichment
- 2026-09-09 11:35 UTCGHSA enrichment
- 2026-09-09 07:49 UTCGHSA enrichment
- 2026-09-09 04:02 UTCGHSA enrichment
- 2026-09-09 00:16 UTCGHSA enrichment
- 2026-09-08 20:30 UTCGHSA enrichment
- 2026-09-08 18:54 UTCCISA KEV update
- 2026-09-08 16:44 UTCGHSA enrichment
- 2026-09-08 12:57 UTCGHSA enrichment
- 2026-09-08 09:08 UTCGHSA enrichment
- 2026-09-08 05:19 UTCGHSA enrichment
- 2026-09-08 01:33 UTCGHSA enrichment
- 2026-09-07 21:47 UTCGHSA enrichment
- 2026-09-07 18:01 UTCGHSA enrichment
- 2026-09-07 14:14 UTCGHSA enrichment
- 2026-09-07 10:25 UTCGHSA enrichment
- 2026-09-07 06:38 UTCGHSA enrichment
- 2026-09-07 02:52 UTCGHSA enrichment
- 2026-09-06 23:03 UTCGHSA enrichment
- 2026-09-06 19:15 UTCGHSA enrichment
- 2026-09-06 15:29 UTCGHSA enrichment
- 2026-09-06 11:42 UTCGHSA enrichment
Publicly available exploits
(10 references)Working exploit code is in the public domain (10 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCWyl-cmd/CVE-2017-7921-Research-ToolkitFirst seen Jan 28, 2026
用于借助FOFA快速测试海康威视的CVE-2017-7921漏洞,并且给出登陆账号和密码,并输出json文件。
Open source ↗ - GitHub PoCvoidsshadows/Hikvision-City-HunterFirst seen Nov 19, 2025
This tool is a modern evolution of older PoCs like those for CVE-2017-7921 and ICSA-17-124-01, updated for 2025 with live console output, threading for speed, and honeypot filtering (skips devices with >12 open ports). It's built for red teamers, bug bounty hunters, and security researchers to identify
Open source ↗ - GitHub PoCaengussong/hikvision_probeFirst seen Nov 26, 2024
Identify hikvision ip and probe for cve-s (CVE-2017-7921, CVE-2022-28171, CVE-2021-36260)
Open source ↗ - GitHub PoCkooroshsanaei/HikVision-CVE-2017-7921First seen Jul 2, 2024
Test For CVE-2017–7921;
Open source ↗ - GitHub PoCK3ysTr0K3R/CVE-2017-7921-EXPLOITFirst seen Jul 24, 2023
A PoC exploit for CVE-2017-7921 - Hikvision Camera Series Improper Authentication Vulnerability.
Open source ↗ - GitHub PoCkrypton612/hikivisionFirst seen Jul 4, 2023
CVE-2017-7921 EXPLOIT
Open source ↗ - GitHub PoC201646613/CVE-2017-7921First seen Jul 20, 2022
CVE-2017-7921-EXP Hikvision camera
Open source ↗ - GitHub PoCalkaid176/CVE-2017-7921First seen Jul 20, 2022
CVE-2017-7921-EXP Hikvision camera
Open source ↗ - GitHub PoCchrisjd20/hikvision_CVE-2017-7921_auth_bypass_config_decryptorFirst seen Jan 29, 2021
This python file will decrypt the configurationFile used by hikvision cameras vulnerable to CVE-2017-7921.
Open source ↗ - GitHub PoCMisakaMikato/cve-2017-7921-golangFirst seen Nov 13, 2020
Hikvision IP camera access bypass exploit, developed by golang.
Open source ↗
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
Frequently asked(6)
What is CVE-2017-7921?
When was CVE-2017-7921 disclosed?
Is CVE-2017-7921 actively exploited?
What is the CVSS score of CVE-2017-7921?
Which products are affected by CVE-2017-7921?
How do I remediate CVE-2017-7921?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-7921
Is Your Infrastructure Affected by CVE-2017-7921?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.