Security readout for executives and security teams
Plain-English summary
SmartBPM.NET 6.70 contains a hard-coded authentication key. A remote attacker who is not logged in may be able to enter the system with regular user privileges, read application data, and perform submission or approval actions. This creates serious confidentiality and workflow-integrity risk.
Executive priority
Treat as urgent for any SmartBPM.NET 6.70 deployment because an unauthenticated remote attacker may gain application access and manipulate business approval workflows. Prioritize exposure reduction and vendor-guided remediation.
Technical view
The issue is CWE-798: use of hard-coded credentials. The CVSS 3.1 score is 9.1, with network access, low complexity, no privileges, and no user interaction required. Reported impact is high confidentiality and integrity loss, with no availability impact stated.
Likely exposure
Exposure is limited to environments running SmartBPM.NET version 6.70. Risk is highest where the application is reachable from the internet, partner networks, or other untrusted segments. The sources do not identify other affected versions.
Exploitation context
The provided sources describe unauthenticated remote exploitation potential, but do not state public exploitation or a public proof of concept. The CVE is not marked as CISA KEV in the supplied bundle, so active exploitation is not confirmed here.
Researcher notes
Evidence is strongest for SmartBPM.NET 6.70 only. The source bundle does not name a patch, fixed version, workaround, exploit artifact, or indicators of compromise. Avoid assuming broader product impact without vendor confirmation.
Mitigation direction
- Identify any SmartBPM.NET 6.70 deployments.
- Check TW-CERT and vendor guidance for fixed versions or official workarounds.
- Restrict network access to trusted users and segments.
- Review whether authentication keys can be rotated under vendor guidance.
- Increase monitoring for unusual workflow submissions or approvals.
Validation and detection
- Confirm installed SmartBPM.NET versions across production and test environments.
- Map whether SmartBPM.NET is reachable from untrusted networks.
- Review logs for unexpected regular-user access or workflow actions.
- Verify any remediation against official vendor or TW-CERT guidance.
- Document compensating controls until vendor remediation is confirmed.
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-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCVE-2023-37287 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
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A: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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.twcert.org.tw/tw/cp-132-7222-cdfd0-1.htmlCVE reference
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.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.