dbcve.org
MyproApplication · Myscada

CVE-2021-33013

HIGH · 7.5 CVSS v3.1 Published 2022-05-13
Fix available
A fix is available. Upgrade to 8.20.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
mySCADA myPRO versions prior to 8.20.0 does not restrict unauthorized read access to sensitive system information.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Information disclosure vulnerability in mySCADA myPRO versions prior to 8.20.0 that allows unauthorized read access to sensitive system information. The lack of access controls permits unauthenticated attackers to potentially view sensitive data, resulting in a HIGH severity rating (CVSS 7.5).

MitigationUpgrade myPRO to version 8.20.0 or later which implements proper restrictions on read access to sensitive system information. If upgrading is not immediately possible, network segmentation and firewall rules should restrict access to the myPRO interface to authorized personnel only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MyproApplication
Affected:< 8.20.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed myPRO version
    Locate the myPRO installation directory and check the version information in the application metadata, About dialog, or version file typically found in the installation folder. Alternatively, access the web interface login page and look for version disclosure in the page source or error messages.
    Affected if The installed version is below 8.20.0
  2. Confirm web interface accessibility
    Verify whether the myPRO web interface is reachable over the network from unauthorized IP addresses by reviewing firewall rules, network configurations, and testing external connectivity to the default web ports (typically 80/443 or custom ports).
    Affected if The myPRO web interface is accessible from untrusted networks without VPN or authentication barriers
  3. Test for unauthenticated information disclosure
    Attempt to access common myPRO endpoints or API paths without providing credentials. Look for responses that return system configuration, project files, user lists, or other sensitive data without requiring login.
    Affected if Sensitive system information is returned without authentication
  4. Review access control configuration
    Inspect the myPRO configuration files or admin settings to determine if read access restrictions are properly enforced on system information endpoints.
    Affected if No access controls are configured or enforced on sensitive data endpoints

You are affected if your installed myPRO version is below 8.20.0 and the web interface is accessible without authentication, allowing unauthorized viewing of sensitive system information.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.20.0 or later
Fixed in 8.20.0
Interim mitigation

Upgrade myPRO to version 8.20.0 or later which implements proper restrictions on read access to sensitive system information. If upgrading is not immediately possible, network segmentation and firewall rules should restrict access to the myPRO interface to authorized personnel only.

Recommended fix High confidence

mySCADA myPRO 8.20.0 or later

  1. Identify the current version of mySCADA myPRO installation
  2. Back up all project files, configurations, and databases before proceeding with the upgrade
  3. Download mySCADA myPRO version 8.20.0 or later from the official mySCADA vendor source (www.myscada.org)
  4. Follow the vendor's documented upgrade procedure for your specific deployment method
  5. After upgrading, verify the new version is 8.20.0 or higher
  6. Test that the access controls now properly restrict unauthorized read access to sensitive system information

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mypro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-33013 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data