CVE-2023-31168
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 · uneditedAn Inclusion of Functionality from Untrusted Control Sphere vulnerability in the Schweitzer Engineering Laboratories SEL-5030 acSELerator QuickSet Software could allow an attacker to embed instructions that could be executed by an authorized device operator. See Instruction Manual Appendix A and Appendix E dated 20230615 for more details. This issue affects SEL-5030 acSELerator QuickSet Software: through 7.1.3.0.
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 confidenceThe SEL-5030 acSELerator QuickSet Software through version 7.1.3.0 contains an Inclusion of Functionality from Untrusted Control Sphere vulnerability (CWE-829), allowing attackers to embed malicious instructions that execute when an authorized device operator runs the software. This represents a code injection or deserialization flaw where untrusted input is processed as executable functionality.
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<= 7.1.3.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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 installed version of SEL-5030 acSELerator QuickSet SoftwareOpen the software and navigate to Help > About, or check the version in Windows Add/Remove Programs, or examine the executable properties in the installation directoryAffected if The software version is 7.1.3.0 or lower
-
Review recently imported project filesInspect the project files or configuration data that have been imported into the software, looking for any unexpected scripts, commands, or serialized data from untrusted sourcesAffected if The software has imported project files or configuration data from untrusted or unknown origins
-
Examine configuration and data files for suspicious contentOpen and inspect configuration files, project files, or data files used by the software for any embedded malicious instructions, unusual code, or serialized objects that were not part of legitimate configurationsAffected if Suspicious or unexpected executable instructions are found within configuration or project files used by the software
If the installed version is 7.1.3.0 or lower and untrusted configuration files or project data have been imported into the software, the environment may be affected by this vulnerability.
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 · scopedApply vendor-provided patches for SEL-5030 acSELerator QuickSet Software to address the untrusted control sphere vulnerability; verify no malicious instructions are embedded in configuration files or project data imported into the software.
SEL-5030 acSELerator QuickSet Software version 7.1.4.0 or later
- 1. Navigate to the SEL customer portal or official SEL website (selinc.com) to obtain the latest version of SEL-5030 acSELerator QuickSet Software.
- 2. Download SEL-5030 acSELerator QuickSet Software version 7.1.4.0 or later.
- 3. Uninstall the current version of the software from the system.
- 4. Install the downloaded fixed version of SEL-5030 acSELerator QuickSet Software.
- 5. Verify the installation by checking the software version to confirm the fix is applied.
- 6. Review the updated Instruction Manual Appendix A and Appendix E for any new security guidance related to untrusted control sphere inclusions.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31168 — 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-31168 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