CVE-2025-67280
SQLi in Tim-Solutions Tim Flow ≤ 9.1.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NSummary
CVE-2025-67280 is a medium-severity SQL Injection: Hibernate (CWE-564) vulnerability in Tim-Solutions Tim Flow. Its CVSS base score is 5.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-1727
Vulnerability Data
In TIM BPM Suite/ TIM FLOW through 9.1.2 multiple Hibernate Query Language injection vulnerabilities exist which allow a low privileged user to extract passwords of other users and access sensitive data of another user.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover dynamic-query construction flaws before deployment.
Input validation directly stops untrusted data from being concatenated into dynamic Hibernate queries.
Requiring documented secure-development standards and tools reduces use of unsafe dynamic SQL patterns.
Secure engineering principles require parameterized queries or ORM-safe APIs instead of string-built SQL.
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 prevent dynamic SQL construction from untrusted input.
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.
Security testing can detect injection flaws but does not prevent them at design time.
Secure SDLC mandates input validation and ORM usage that reduce dynamic SQL injection risk.
Application security requirements include secure query construction and ORM parameter binding.
Secure architecture principles discourage dynamic SQL but do not directly address Hibernate misuse.
Secure coding explicitly requires parameterized queries and safe Hibernate usage to prevent injection.
Access restrictions limit data exposure but do not stop injection into queries.