Sel 5030 Acselerator QuicksetApplication · Selinc

CVE-2023-31170

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-31
Fix available
A fix is available. Upgrade to after 7.1.3.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
An 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 confidence

The SEL-5030 acSELerator QuickSet Software contains a vulnerability where an attacker can embed malicious instructions within files or data that get processed when an authorized operator uses the software. This allows execution of attacker-controlled functionality through the trusted operator's session, likely via insecure deserialization, script injection, or unsafe file/include processing.

MitigationApply vendor patches when available; avoid opening untrusted QuickSet project files, configurations, or attachments from unverified sources; implement network segmentation and least-privilege access for operators managing SEL devices.

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
Sel 5030 Acselerator QuicksetApplication
Affected:<= 7.1.3.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed QuickSet version
    Open the QuickSet application and navigate to Help > About, or check Programs and Features in Windows Control Panel for the installed version of SEL-5030 acSELerator QuickSet
    Affected if The installed version is 7.1.3.0 or any earlier version (any version <= 7.1.3.0)
  2. Identify project file sources
    Review recent QuickSet project files (.qsp, .sel, .xml or other project/config files) that have been opened. Check the default project directory and recent files list within the application
    Affected if Any project files from untrusted or unknown sources have been opened in the software
  3. Inspect application data directories
    Check user-accessible directories where QuickSet stores project files, configurations, and exports (typically under Documents or AppData folders) for unexpected or suspicious files with unusual extensions
    Affected if Unexpected files with potentially malicious content are present in QuickSet data directories
  4. Review deserialization and file processing behavior
    Monitor or inspect the QuickSet application logs and any configurable settings related to file deserialization, script execution, or external file inclusion (check application preferences or configuration files if accessible)
    Affected if File deserialization, script execution, or external file inclusion features are enabled or used without verification

You are affected if the installed QuickSet version is 7.1.3.0 or earlier AND any untrusted or suspicious project files have been opened in the software.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 7.1.3.0
Interim mitigation

Apply vendor patches when available; avoid opening untrusted QuickSet project files, configurations, or attachments from unverified sources; implement network segmentation and least-privilege access for operators managing SEL devices.

Fix this in Sel 5030 Acselerator Quickset Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31170 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31170 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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