CVE-2026-31928 — Daktronics DMP-5000 Default Administrative Account Vulnerability
The DMP-5000 devices are shipped with a default administrative web account with weak authentication controls, which are not required to be changed during initial configuration or operation. Using these accounts provides full system access.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.6% (30-day exploitation probability)+7
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Daktronics DMP-5000, Daktronics Dmp-5000 Firmware, Daktronics DMP-8000…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Daktronics | DMP-5000 | < v9.43.x.x< v8.117.x.x< v10.34.x.x | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Daktronics | Dmp-5000 Firmware | ≥ 9.0.0.0 and < 9.43.0.0≥ 10.0.0.0 and < 10.34.0.0< 8.117.0.0 | Vulnerable | NIST National Vulnerability Database |
| Daktronics | DMP-8000 | < v9.43.x.x< v8.117.x.x< v10.34.x.x | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Daktronics | Dmp-8000 Firmware | ≥ 10.0.0.0 and < 10.34.0.0≥ 9.0.0.0 and < 9.43.0.0< 8.117.0.0 | Vulnerable | NIST National Vulnerability Database |
| Daktronics | VFC-DMP-5000 | < v8.117.x.x< v9.43.x.x< v10.34.x.x | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Daktronics | Vfc-dmp-5000 Firmware | ≥ 10.0.0.0 and < 10.34.0.0≥ 9.0.0.0 and < 9.43.0.0< 8.117.0.0 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.3 | CVSS 4.0 | Critical | — | — | ics-cert@hq.dhs.gov via NIST National Vulnerability Database |
| 9.3 | CVSS 4.0 | Critical | — | — | icscert via CVE Program (cve.org) e CISA ADP |
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 8.1 | CVSS 3.1 | High | 2.8 | 5.2 | ics-cert@hq.dhs.gov via NIST National Vulnerability Database |
| 8.1 | CVSS 3.1 | High | — | — | icscert via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.57%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
Analysis and videos
CVE-2026-31928: Daktronics DMP-5000 Default Administrative Account Vulnerability
Daktronics DMP-5000, DMP-8000 and VFC-DMP-5000 firmware ship with a default administrative web account that has weak authentication controls and is not required to be changed during setup or operation. According to the record, use of these accounts provides full system access. NVD rates the issue 9.8 (critical) under CVSS 3.1, and no confirmed exploitation appears in the sources consulted.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · daktronics/vfc-dmp-5000, daktronics/dmp-5000, daktronics/dmp-8000
- SSVC assessment updated
- Record published
- CVSS changed · 9.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-28701 Daktronics Controller Firmware Path Traversal Jun 26, 2026
- High CVE-2026-33560 Daktronics Controller Firmware Unrestricted Upload of File with Dangerous Type Jun 26, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-31928 is "Daktronics DMP-5000 Default Administrative Account Vulnerability", rated Critical. It affects DMP-5000 (Daktronics); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 0.57% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.