Security readout for executives and security teams
Plain-English summary
SmartBPM.NET 6.70 contains a hard-coded machine key. A remote unauthenticated attacker could use that key to send malicious serialized data, potentially running code on the server and causing service disruption.
Executive priority
Treat this as urgent for any exposed SmartBPM.NET 6.70 system. Remote unauthenticated code execution can lead to system compromise, data loss, and downtime. Prioritize inventory, exposure reduction, and vendor-confirmed remediation.
Technical view
The issue is CWE-798 in SmartSoft SmartBPM.NET 6.70. The public description says the hard-coded machine key can let an unauthenticated remote attacker submit serialized payloads to achieve arbitrary code execution, with full confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most relevant for organizations running SmartBPM.NET 6.70, especially if reachable from the internet or untrusted networks. The source bundle does not identify other affected versions or CPEs.
Exploitation context
The CVE is not marked as CISA KEV, and the provided sources do not cite active exploitation. The vulnerability is still high urgency because it is remote, unauthenticated, low complexity, and rated CVSS 9.8.
Researcher notes
The bundle provides a concise vulnerability statement but limited operational detail. It does not name a fixed version, workaround, exploit in the wild, or affected versions beyond 6.70. Avoid assuming broader SmartBPM.NET exposure without vendor confirmation.
Mitigation direction
- Identify all SmartBPM.NET deployments and confirm whether version 6.70 is present.
- Check SmartSoft and TWCERT guidance for an official fix or supported workaround.
- Restrict external access to SmartBPM.NET until remediation is confirmed.
- Increase monitoring for unusual application errors, serialized request handling, and unexpected process behavior.
- Prepare incident response review for exposed systems running the affected version.
Validation and detection
- Inventory internet-facing and internal SmartBPM.NET instances.
- Confirm product version directly from administrative records or vendor-supported interfaces.
- Verify whether affected systems are reachable from untrusted networks.
- Review vendor and TWCERT advisories for patch or workaround status.
- Check logs for suspicious requests or abnormal server-side execution indicators.
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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-37286 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.8 (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:H
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:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.twcert.org.tw/tw/cp-132-7221-438c6-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.