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
- 100.0%
- KEV
- ⚠ Exploited
Published
May 6, 2017
Last Modified
April 22, 2026
Advisory Details (4)
Auto-updated May 12, 2026Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 42× in last 7d / 198× 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 393 total refreshes for this CVE.
- 2026-07-23 01:30 UTCEG score recompute
- 2026-07-23 00:07 UTCEG score recompute
- 2026-07-23 00:07 UTCGHSA enrichment
- 2026-07-22 22:10 UTCEG score recompute
- 2026-07-22 20:19 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 16:32 UTCGHSA enrichment
- 2026-07-22 12:45 UTCGHSA enrichment
- 2026-07-22 08:58 UTCGHSA enrichment
- 2026-07-22 05:13 UTCGHSA enrichment
- 2026-07-22 00:53 UTCGHSA enrichment
- 2026-07-21 18:44 UTCGHSA enrichment
- 2026-07-21 14:55 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 11:09 UTCGHSA enrichment
- 2026-07-21 07:21 UTCGHSA enrichment
- 2026-07-21 03:36 UTCGHSA enrichment
- 2026-07-20 23:49 UTCGHSA enrichment
- 2026-07-20 20:01 UTCGHSA enrichment
- 2026-07-20 16:15 UTCGHSA enrichment
- 2026-07-20 12:29 UTCGHSA enrichment
- 2026-07-20 08:42 UTCGHSA enrichment
- 2026-07-20 04:56 UTCGHSA enrichment
- 2026-07-20 01:09 UTCGHSA enrichment
- 2026-07-19 21:23 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-19 17:37 UTCGHSA enrichment
- 2026-07-19 13:51 UTCGHSA enrichment
- 2026-07-19 10:05 UTCGHSA enrichment
- 2026-07-19 06:19 UTCGHSA enrichment
- 2026-07-19 02:32 UTCGHSA enrichment
- 2026-07-18 22:47 UTCGHSA enrichment
- 2026-07-18 19:00 UTCGHSA enrichment
- 2026-07-18 15:13 UTCGHSA enrichment
- 2026-07-18 11:26 UTCGHSA enrichment
- 2026-07-18 07:40 UTCGHSA enrichment
- 2026-07-18 03:54 UTCGHSA enrichment
- 2026-07-18 00:07 UTCGHSA enrichment
- 2026-07-17 20:21 UTCGHSA enrichment
- 2026-07-17 16:35 UTCGHSA enrichment
- 2026-07-17 12:48 UTCGHSA enrichment
- 2026-07-17 09:02 UTCEG score recompute
- 2026-07-17 09:02 UTCGHSA enrichment
- 2026-07-17 05:16 UTCGHSA enrichment
- 2026-07-17 01:30 UTCGHSA enrichment
- 2026-07-16 21:44 UTCGHSA enrichment
- 2026-07-16 17:58 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 14:11 UTCGHSA enrichment
- 2026-07-16 10:25 UTCGHSA enrichment
- 2026-07-16 06:39 UTCGHSA enrichment
- 2026-07-16 02:53 UTCGHSA enrichment
- 2026-07-15 23:07 UTCGHSA enrichment
- 2026-07-15 19:21 UTCGHSA enrichment
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:35 UTCGHSA enrichment
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 11:49 UTCGHSA enrichment
- 2026-07-15 08:03 UTCGHSA enrichment
- 2026-07-15 04:16 UTCGHSA enrichment
- 2026-07-15 00:28 UTCGHSA enrichment
- 2026-07-14 20:40 UTCGHSA enrichment
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 16:54 UTCGHSA enrichment
- 2026-07-14 13:08 UTCGHSA enrichment
- 2026-07-14 09:22 UTCGHSA enrichment
- 2026-07-14 05:36 UTCGHSA enrichment
- 2026-07-14 01:50 UTCGHSA enrichment
- 2026-07-13 22:05 UTCGHSA enrichment
- 2026-07-13 18:19 UTCGHSA enrichment
- 2026-07-13 17:07 UTCCISA KEV update
- 2026-07-13 14:32 UTCGHSA enrichment
- 2026-07-13 10:46 UTCGHSA enrichment
- 2026-07-13 06:59 UTCGHSA enrichment
- 2026-07-13 03:12 UTCGHSA enrichment
- 2026-07-12 23:25 UTCGHSA enrichment
- 2026-07-12 19:39 UTCGHSA enrichment
- 2026-07-12 15:53 UTCGHSA enrichment
- 2026-07-12 12:07 UTCGHSA enrichment
- 2026-07-12 08:21 UTCGHSA enrichment
- 2026-07-12 04:35 UTCGHSA enrichment
- 2026-07-12 00:49 UTCGHSA enrichment
- 2026-07-11 21:02 UTCGHSA enrichment
- 2026-07-11 17:15 UTCGHSA enrichment
- 2026-07-11 13:29 UTCGHSA enrichment
- 2026-07-11 09:43 UTCGHSA enrichment
- 2026-07-11 05:57 UTCGHSA enrichment
- 2026-07-11 02:11 UTCGHSA enrichment
- 2026-07-10 22:23 UTCGHSA enrichment
- 2026-07-10 18:33 UTCGHSA enrichment
- 2026-07-10 17:52 UTCCISA KEV update
- 2026-07-10 14:47 UTCGHSA enrichment
- 2026-07-10 11:01 UTCGHSA enrichment
- 2026-07-10 07:13 UTCGHSA enrichment
- 2026-07-10 03:25 UTCGHSA enrichment
- 2026-07-09 23:40 UTCGHSA enrichment
- 2026-07-09 19:53 UTCGHSA enrichment
- 2026-07-09 16:07 UTCGHSA enrichment
- 2026-07-09 12:21 UTCGHSA enrichment
- 2026-07-09 08:35 UTCGHSA enrichment
- 2026-07-09 04:48 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 PoC201646613/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 ↗ - GitHub PoCBurnyMcDull/CVE-2017-7921First seen Nov 12, 2020
海康威视未授权访问检测poc及口令爆破
Open source ↗ - GitHub PoCJrDw0/CVE-2017-7921-EXPFirst seen Apr 27, 2020
Hikvision camera CVE-2017-7921-EXP
Open source ↗
Related CVEs(same CWE)
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.