Skip to content

Product

myscada mypro vulnerabilities

28 published CVES affecting myscada mypro, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
28
Critical
12
High
13
Medium
3
Low
0
Unscored
0
CISA KEV
0

Latest myscada mypro CVEs

Newest publication first · page 1 of 2

  1. MediumCVSS 5.1 EPSS 0.60%

    mySCADA myPRO Manager is vulnerable to cross-site request forgery (CSRF), which could allow an attacker to obtain sensitive information. An attacker would need to trick the victim in to visiting an attacker-controlled website.

  2. CVE-2023-28400 CVE-2023-28400

    Published
    HighCVSS 8.8 EPSS 24.6%

    mySCADA myPRO versions 8.26.0 and prior has parameters which an authenticated user could exploit to inject arbitrary operating system commands.

  3. CVE-2023-28716 CVE-2023-28716

    Published
    HighCVSS 8.8 EPSS 4.5%

    mySCADA myPRO versions 8.26.0 and prior has parameters which an authenticated user could exploit to inject arbitrary operating system commands.

  4. CVE-2023-28384 CVE-2023-28384

    Published
    HighCVSS 8.8 EPSS 44.8% Framework module

    mySCADA myPRO versions 8.26.0 and prior has parameters which an authenticated user could exploit to inject arbitrary operating system commands.

  5. CVE-2023-29169 CVE-2023-29169

    Published
    HighCVSS 8.8 EPSS 0.75%

    mySCADA myPRO versions 8.26.0 and prior has parameters which an authenticated user could exploit to inject arbitrary operating system commands.

  6. CVE-2023-29150 CVE-2023-29150

    Published
    HighCVSS 8.8 EPSS 0.75%

    mySCADA myPRO versions 8.26.0 and prior has parameters which an authenticated user could exploit to inject arbitrary operating system commands.

  7. HighCVSS 8.8 EPSS 1.4%

    An authenticated user may be able to misuse parameters to inject arbitrary operating system commands into mySCADA myPRO versions 8.25.0 and prior.

  8. CVE-2021-43985 mySCADA myPRO

    Published
    CriticalCVSS 9.8 EPSS 1.6%

    An unauthenticated remote attacker can access mySCADA myPRO Versions 8.20.0 and prior without any form of authentication or authorization.

  9. CVE-2021-43989 mySCADA myPRO

    Published
    HighCVSS 7.5 EPSS 0.69%

    mySCADA myPRO Versions 8.20.0 and prior stores passwords using MD5, which may allow an attacker to crack the previously retrieved password hashes.

  10. CVE-2021-43981 mySCADA myPRO

    Published
    CriticalCVSS 9.8 EPSS 1.3%

    mySCADA myPRO: Versions 8.20.0 and prior has a feature to send emails, which may allow an attacker to inject arbitrary operating system commands through a specific parameter.

  11. CVE-2021-44453 mySCADA myPRO

    Published
    CriticalCVSS 9.8 EPSS 1.5%

    mySCADA myPRO: Versions 8.20.0 and prior has a vulnerable debug interface which includes a ping utility, which may allow an attacker to inject arbitrary operating system commands.

  12. CVE-2021-43984 mySCADA myPRO

    Published
    CriticalCVSS 9.8 EPSS 1.3%

    mySCADA myPRO: Versions 8.20.0 and prior has a feature where the firmware can be updated, which may allow an attacker to inject arbitrary operating system commands through a specific parameter.

  13. CVE-2021-43987 mySCADA myPRO

    Published
    CriticalCVSS 9.8 EPSS 1.3%

    An additional, nondocumented administrative account exists in mySCADA myPRO Versions 8.20.0 and prior that is not exposed through the web interface, which cannot be deleted or changed through the regular web interface.

  14. CVE-2021-22657 mySCADA myPRO

    Published
    CriticalCVSS 9.8 EPSS 1.3%

    mySCADA myPRO: Versions 8.20.0 and prior has a feature where the API password can be specified, which may allow an attacker to inject arbitrary operating system commands through a specific parameter.

  15. CVE-2021-23198 mySCADA myPRO

    Published
    CriticalCVSS 9.8 EPSS 1.3%

    mySCADA myPRO: Versions 8.20.0 and prior has a feature where the password can be specified, which may allow an attacker to inject arbitrary operating system commands through a specific parameter.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.