CVE-2021-33005
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 · uneditedmySCADA myPRO versions prior to 8.20.0 allows an unauthenticated remote attacker to upload arbitrary files to arbitrary directories.
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 · high confidencemySCADA myPRO versions prior to 8.20.0 contain an arbitrary file upload vulnerability that allows unauthenticated remote attackers to upload files to any directory on the system. This can lead to remote code execution by placing malicious files in web-accessible directories.
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< 8.20.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify mySCADA myPRO versionAccess the web interface or check system documentation to determine the installed version numberAffected if The installed version is below 8.20.0 (e.g., 8.19.0, 8.18.0, earlier versions)
-
Confirm myPRO web server is runningCheck if the myPRO web interface is accessible on the network by accessing the application URLAffected if The web interface is exposed and reachable from the network
-
Verify upload functionality is accessible without authenticationAttempt to access the file upload endpoint or check if the web application allows unauthenticated file upload requestsAffected if File upload can be performed without requiring user authentication
-
Check if uploaded files can be placed in web-accessible directoriesExamine the web server configuration to determine if arbitrary directories are writable and accessible via HTTPAffected if The web server allows uploaded files to be stored in directories accessible via HTTP/HTTPS
You are affected if your mySCADA myPRO installation is version 8.19.0 or earlier AND the web interface is network-accessible without authentication protections.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.20.0
Upgrade to mySCADA myPRO version 8.20.0 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the mySCADA interface using firewall rules or network segmentation.
8.20.0
- 1. Identify all systems running mySCADA myPRO.
- 2. Verify current version of mySCADA myPRO on each system.
- 3. For any system running a version prior to 8.20.0, download mySCADA myPRO version 8.20.0 or later from the official vendor (www.myscada.org).
- 4. Follow the vendor's documented upgrade procedure to apply the update.
- 5. After upgrading, verify that the new version 8.20.0 is correctly installed.
- 6. Test that the path traversal vulnerability is no longer exploitable.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-33005 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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