Broken or risky cryptographic algorithm in mySCADA myPRO
Priority LOW 34CWE-916Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-327.
Summary
mySCADA myPRO Versions 8.20.0 and prior stores passwords using MD5, which may allow an attacker to crack the previously retrieved password hashes.
Why it matters now
EPSS 0.00692 53rd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2021-43989
- 2026-10-03 Alias added: GHSA-5xc5-crm5-w93r
- 2026-10-16 EPSS moved to the 50th–90th percentile
References
More mySCADA Mypro vulnerabilities
- TI-2022-02063 mySCADA myPRO Command Injection CVSS 3.1CRITICAL 9.9
- TI-2023-12930 OS command injection in mySCADA myPRO CVSS 3.1HIGH 8.8
- TI-2023-12946 OS command injection in mySCADA myPRO CVSS 3.1HIGH 8.8
- TI-2025-18574 mySCADA myPRO Manager Missing Authentication for Critical Function CVSS 4.0CRITICAL 10.0
- TI-2018-08060 A hardcoded FTP username of myscada and password of Vikuk63 in 'myscadagate.exe' in… CVSS 3.0CRITICAL 9.1
- TI-2025-16762 mySCADA myPRO Manager Cleartext Storage of Sensitive Information CVSS 4.0CRITICAL 9.2
Sources
- CVE-2021-43989 · CVE Program
- CVE-2021-43989 · NVD
- FIRST EPSS
- GHSA-5xc5-crm5-w93r · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences