CVE-2023-1034
Salesagility Suitecrm ≤ 7.12.9
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-1034 is a high-severity Path Traversal: '\..\filename' (CWE-29) vulnerability in Salesagility Suitecrm. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-23325
Vulnerability Data
Path Traversal: '\..\filename' in GitHub repository salesagility/suitecrm prior to 7.12.9.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that block this traversal vector.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Application security requirements can mandate input validation and path canonicalization to block traversal sequences.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, hardening, design review against attack patterns) that reach path-traversal neutralization in many but not all cases; business-process-specific controls, outsourced development, and residual design choices leave a bounded remainder unaddressed.
Secure coding standards directly require neutralizing path traversal sequences such as '\..\filename'.
Security testing can discover path-traversal flaws but does not itself prevent them in production code.