CVE-2023-6448
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 · uneditedUnitronics VisiLogic before version 9.9.00, used in Vision and Samba PLCs and HMIs, uses a default administrative password. An unauthenticated attacker with network access can take administrative control of a vulnerable system.
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 confidenceUnitronics VisiLogic software versions prior to 9.9.00 used in Vision and Samba PLCs and HMIs contains a hardcoded/default administrative password. An unauthenticated attacker with network access can authenticate using these default credentials and gain full administrative control of the industrial controller.
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< 12.38< 12.38< 12.38< 12.38< 12.38< 12.38< 12.38< 12.38CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 VisiLogic software versionOpen VisiLogic and navigate to Help > About, or check the installation directory for version information. Compare the version number to 9.9.00.Affected if VisiLogic version is prior to 9.9.00
-
Identify PLC/HMI device firmware versionConnect to the Unitronics device via VisiLogic or access the device web interface/status page. Navigate to System > Info or similar to view the firmware version.Affected if Device firmware version is < 12.38 (for Vision1210, Vision1040, Vision700, Vision570, Vision560, Vision430, Vision350, or Vision130)
-
Verify default administrative password statusAttempt to log into the PLC/HMI device web interface or via VisiLogic using the default administrator account. Check if authentication succeeds without a changed password.Affected if The default administrative password has not been changed from factory default
-
Check network exposure of deviceReview network configuration and firewall rules to determine if the PLC/HMI management interface (typically ports 80, 443, or 20256) is accessible from untrusted networks.Affected if Device is directly accessible from untrusted networks without firewall segmentation
Your environment is affected if you run VisiLogic versions prior to 9.9.00 with any Vision PLC/HMI device (firmware < 12.38) that still uses the factory default administrative password and is network-accessible.
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 · scoped12.38
Immediately change the default administrative password on all affected Unitronics VisiLogic installations, update to version 9.9.00 or later, and implement network segmentation to restrict access to PLCs and HMIs from untrusted networks.
VisiLogic version 9.9.00 and PLC/HMI Firmware version 12.38
- Upgrade the Unitronics VisiLogic programming software to version 9.9.00 or later from the official Unitronics downloads page (downloads.unitronicsplc.com)
- Upgrade the PLC/HMI device firmware to version 12.38 or later. This can typically be done through VisiLogic software by connecting to the device and using the 'Firmware Update' or 'OS Download' function
- After upgrading, change the default administrative password immediately through the VisiLogic software or the device's web interface
- If upgrading is not immediately possible, implement network segmentation to isolate the PLC/HMI from untrusted networks and restrict access to authorized personnel only
- Enable logging and monitoring for unauthorized access attempts
- Consider implementing additional access controls such as VPNs or firewall rules to limit exposure to the management interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing4.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 $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6448 — 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-6448 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