CVE-2016-5678
No exploitation reported by the sources we read.
- Published2016-08-31
- WeaknessCWE-798
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
NUUO NVRmini 2 1.0.0 through 3.0.0 and NUUO NVRsolo 1.0.0 through 3.0.0 have hardcoded root credentials, which allows remote attackers to obtain administrative access via unspecified vectors.
Timeline
dates in UTC- 2016-08-3115:59CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-5678?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-5678?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | = 1.0.0 | no fix published | NVD |
| 1.1 | = 1.1.0 | no fix published | NVD |
| 1.3 | = 1.3.0 | no fix published | NVD |
| 1.3 | = 1.3.2 | no fix published | NVD |
| 1.4 | = 1.4.0 | no fix published | NVD |
| 1.5 | = 1.5.1 | no fix published | NVD |
| 1.5 | = 1.5.2 | no fix published | NVD |
| 1.6 | = 1.6.0 | no fix published | NVD |
| 1.6 | = 1.6.1 | no fix published | NVD |
| 1.6 | = 1.6.2 | no fix published | NVD |
| 1.6 | = 1.6.4 | no fix published | NVD |
| 1.7 | = 1.7.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | = 1.0.0 | no fix published | NVD |
| 1.0 | = 1.0.1 | no fix published | NVD |
| 1.1 | = 1.1.0 | no fix published | NVD |
| 1.1 | = 1.1.0.117 | no fix published | NVD |
| 1.1 | = 1.1.1 | no fix published | NVD |
| 1.1 | = 1.1.2 | no fix published | NVD |
| 1.2 | = 1.2.0 | no fix published | NVD |
| 1.3 | = 1.3.0 | no fix published | NVD |
| 1.75 | = 1.75 | no fix published | NVD |
| 2.0 | = 2.0.0 | no fix published | NVD |
| 2.0 | = 2.0.1 | no fix published | NVD |
| 2.1 | = 2.1.5 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.010read 2026-10-23
- NVDweakness (CWE)CWE-798read 2026-10-23
- FIRST EPSSEPSS score8.7 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2016-08-31
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-5678?
Is CVE-2016-5678 actively exploited?
What is the CVSS score for CVE-2016-5678?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.