Security readout for executives and security teams
Plain-English summary
SprintWork 2.3.1 on Windows has local permission weaknesses that can let a standard local user gain full administrative control. This is not described as a remote break-in by itself, but it can turn a low-privilege foothold into complete system compromise.
Executive priority
Treat as high priority for endpoints where SprintWork 2.3.1 is deployed and local user access is common. It is less urgent than internet-facing remote code execution, but serious because it can convert a limited compromise into full machine control.
Technical view
The CVE describes multiple local privilege escalation issues in SprintWork 2.3.1 caused by insecure file, service, and folder permissions on Windows. The reported impact is creation of an administrative user and complete system access. CVSS 4.0 is 8.5 High with local attack vector and low complexity.
Likely exposure
Organizations are likely exposed only where Veridium SprintWork 2.3.1 is installed on Windows systems. Risk is higher on shared workstations, kiosks, or endpoints where non-admin users can log in locally, or where an attacker may already have user-level access.
Exploitation context
A public Exploit-DB reference exists, but the provided sources do not show confirmed active exploitation or CISA KEV listing. Exploitation requires local low-privilege access, so this is mainly a post-compromise or insider-risk escalation issue.
Researcher notes
Evidence is limited to the CVE record, VulnCheck advisory, vendor/product pages, and an Exploit-DB entry. No official patch details are included in the provided bundle. Do not assume exploitation in the wild without additional evidence.
Mitigation direction
- Identify Windows systems running SprintWork 2.3.1.
- Check Veridium guidance for fixed versions or vendor-recommended remediation.
- Upgrade, remove, or disable SprintWork where business need is limited.
- Restrict local interactive access to affected systems.
- Review service, folder, and executable permissions for unsafe write access.
- Prioritize remediation on shared or high-value endpoints.
Validation and detection
- Inventory installed SprintWork versions on Windows endpoints.
- Confirm whether version 2.3.1 is present.
- Review local service permissions for non-admin modification rights.
- Review installation folders for non-admin write permissions.
- Check whether vendor advisories or updates supersede version 2.3.1.
- Monitor affected hosts for unexpected local administrator account changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-276: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-37160 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.5 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.5HighVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-48070CVE reference · exploit
- Vendor HomepageCVE reference · product
- Product Information PageCVE reference · product
- VulnCheck Advisory: SprintWork 2.3.1 - Local Privilege EscalationCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Default Permissions
Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.