CVE-2023-28384
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 8.26.0 and prior has parameters which an authenticated user could exploit to inject arbitrary operating system commands.
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 confidencemySCADA myPRO versions 8.26.0 and prior contains an OS command injection vulnerability where authenticated users can inject arbitrary operating system commands through certain parameters. This is a critical security flaw that allows complete compromise of the underlying system by malicious authenticated users.
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.26.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed mySCADA myPRO versionCheck the application's About page, or look in the installation directory for version files. Common locations include the installation folder's version.txt or within the myPRO application data directories.Affected if The installed version is 8.26.0 or any version prior to 8.26.0
-
Determine if web interface is accessibleAttempt to access the mySCADA myPRO web interface via HTTP/HTTPS on the default ports (typically 8080 or 8443). Check if the login page is reachable.Affected if The web interface is exposed and reachable from the network
-
Check for active user sessionsReview application logs or session management to see if multiple authenticated user accounts exist. Since the vulnerability requires authentication, identify if any non-administrator accounts have access.Affected if There are authenticated user accounts (other than administrators) with access to the system
-
Review application logs for suspicious commandsExamine mySCADA myPRO application logs for entries containing unusual or unexpected operating system command patterns, especially those with shell metacharacters like ; | & $ or backticks.Affected if Logs show OS command patterns that do not correspond to expected system operations
-
Inspect for unauthorized processes or network connectionsUse system utilities (netstat, process monitor) on the host running mySCADA myPRO to identify unexpected outbound connections or spawned processes, particularly those initiated by the myPRO service account.Affected if Unexpected network connections or processes are observed originating from the myPRO application
You are affected if your mySCADA myPRO installation is version 8.26.0 or prior AND the web interface is accessible to authenticated users on your network.
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.
From vendor dataUpgrade to a patched version of mySCADA myPRO (if available) or implement proper input validation and sanitization on all user-supplied parameters, avoiding direct shell command execution where possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28384 — 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-2023-28384 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