CVE-2023-28400
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 · high confidencemySCADA myPRO versions 8.26.0 and prior contains an authenticated command injection vulnerability where user-supplied parameters are not properly sanitized before being passed to operating system command execution, allowing authenticated users to execute arbitrary OS commands.
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.
-
Confirm mySCADA myPRO installationLook for the mySCADA myPRO service/process on the system, or check common installation directories such as C:\Program Files\mySCADA or /opt/myscada on Linux systemsAffected if mySCADA myPRO software is found running on the system
-
Identify installed versionCheck the version of mySCADA myPRO by accessing the web interface and viewing the About/Help section, or check version files in the installation directory such as version.txt or myPRO.iniAffected if The installed version is 8.26.0 or any prior version (versions <= 8.26.0 are affected)
-
Verify web interface accessibilityCheck if the mySCADA web interface is accessible on common ports (typically 8080, 8443, or 80/443). Use a browser or curl to confirm the interface respondsAffected if The mySCADA web interface is exposed and reachable from the network
-
Review user account configurationAccess the mySCADA administration panel and list configured user accounts. Check for any unexpected or unauthorized user accounts in the user management sectionAffected if There are user accounts configured (the vulnerability requires authenticated access)
-
Inspect system for suspicious command executionReview mySCADA logs (typically in the logs/ directory within the installation folder) and system process logs for any unexpected or unauthorized command execution entries, especially those involving shell commands or system utilitiesAffected if Unexpected commands, shell invocations, or suspicious log entries are found in mySCADA or system logs
A system is affected if mySCADA myPRO version 8.26.0 or prior is installed and the web interface is accessible to authenticated users.
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 dataRestrict access to trusted authenticated users only, implement least-privilege access controls, and upgrade to a patched version once available.
- 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-28400 — 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-28400 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