{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-26671 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-26671 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-26671 is a high-severity vulnerability in TAIWAN SECOM CO., LTD., Personnel Attendance Management system, published on 7 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-26671 and fix it if it is affected.\n\nWhat it is: CVE-2022-26671 is a high-severity vulnerability in TAIWAN SECOM CO., LTD., Personnel Attendance Management system, published on 7 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-26671 in the wild and no public exploit code.\n\nAffected product: TAIWAN SECOM CO., LTD., Personnel Attendance Management system. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-26671/ (Markdown: https://insights.sbomify.com/CVE-2022-26671/index.md)","id":"CVE-2022-26671","markdown":"https://insights.sbomify.com/CVE-2022-26671/index.md","name":"CVE-2022-26671","record":{"aliases":["GHSA-j2pm-2c5g-ch2x"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Access Control System","requires_auth":"none","summary":"An unauthenticated remote attacker can use hard-coded credentials to access the Dr.ID system, read information, and modify settings.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"twcert","cpe":[{"product":"dr.id_access_control","vendor":"secom"},{"product":"dr.id_attendance_system","vendor":"secom"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Taiwan Secom Dr.ID Access Control system’s login page has a hard-coded credential in the source code. An unauthenticated remote attacker can use the hard-coded credential to acquire partial system information and modify system setting to cause partial disrupt of service.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-07-22","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-07-22T19:49:51Z","kind":"github_poc","ref":"https://github.com/DefensiveOrigins/POC-CVE-2022-26671","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"TAIWAN SECOM CO., LTD., a xDoor Access Control and Personnel Attendance Management system - Hard-coded Credentials","id":"CVE-2022-26671","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"ASUS WebStorage - Use of Hard-coded Credentials","id":"CVE-2022-26672"},"packages":[],"prev":{"headline":"D-Link DIR-878 - Command Injection","id":"CVE-2022-26670"},"products":["Personnel Attendance Management system"],"published":"2022-04-07","related":[{"cvss_score":9.8,"headline":"SECOM Dr.ID Access control system - SQL injection","id":"CVE-2024-7731","kev_date_added":null,"published":"2024-08-14"},{"cvss_score":9.8,"headline":"TAIWAN SECOM CO., LTD., Door Access Control and Personnel Attendance Management system - Use of Hard-coded Credentials","id":"CVE-2021-35961","kev_date_added":null,"published":"2021-07-16"},{"cvss_score":9.8,"headline":"TAIWAN SECOM CO., LTD. - Pre-auth SQL Injection","id":"CVE-2020-3934","kev_date_added":null,"published":"2020-02-11"},{"cvss_score":7.5,"headline":"TAIWAN SECOM CO., LTD. – Sensitivity Information Exposure","id":"CVE-2020-3935","kev_date_added":null,"published":"2020-02-11"},{"cvss_score":5.3,"headline":"TAIWAN SECOM CO., LTD. - User Account Enumeration","id":"CVE-2020-3933","kev_date_added":null,"published":"2020-02-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["TAIWAN SECOM CO., LTD.,"]},"summary":"An unauthenticated remote attacker can use hard-coded credentials to access the Dr.ID system, read information, and modify settings.","url":"https://insights.sbomify.com/CVE-2022-26671/"}