TAIWAN SECOM CO., LTD. - Pre-auth SQL Injection
Priority MEDIUM 45CWE-89Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- SQL injection
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-89.
Summary
TAIWAN SECOM CO., LTD., a Door Access Control and Personnel Attendance Management system, contains a vulnerability of Pre-auth SQL Injection, allowing attackers to inject a specific SQL command.
Why it matters now
EPSS 0.01386 72nd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| SECOM | Door Access Control system | up to 3.3.2 | — | No fix listed | CNA |
| SECOM | Personnel Attendance system | up to 3.3.0.3_20160517 | — | No fix listed | CNA |
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2020-3934
- 2026-10-03 Alias added: GHSA-h52j-fhqv-qpvw
References
More SECOM Dr.id Access Control vulnerabilities
- TI-2024-07166 SECOM Dr.ID Access control system - SQL injection CVSS 3.1CRITICAL 9.8
- TI-2021-14414 TAIWAN SECOM CO., LTD., Door Access Control and Personnel Attendance Management system - Use of Hard-coded Credentials CVSS 3.1CRITICAL 9.8
- TI-2020-03435 TAIWAN SECOM CO., LTD. – Sensitivity Information Exposure CVSS 3.1HIGH 7.5
- TI-2022-09942 TAIWAN SECOM CO., LTD., a xDoor Access Control and Personnel Attendance Management system - Hard-coded Credentials CVSS 3.1HIGH 7.3
- TI-2020-03433 TAIWAN SECOM CO., LTD. - User Account Enumeration CVSS 3.1MEDIUM 5.3
Sources
- CVE-2020-3934 · CVE Program
- CVE-2020-3934 · NVD
- FIRST EPSS
- GHSA-h52j-fhqv-qpvw · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences