CVE-2022-26671
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTaiwan 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Taiwan Secom Dr.ID Access Control system’s login page contains a hard-coded credential embedded in the source code. An unauthenticated remote attacker can leverage this credential to bypass authentication, access partial system information, modify system settings, and disrupt service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.3.2= 3.4.0.0.3.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of Secom Dr.ID productAccess the system administration panel or check the software inventory to determine if the installed version is either Dr.ID Access Control 3.3.2 or Dr.ID Attendance System 3.4.0.0.3.11Affected if The installed version matches exactly 3.3.2 for Access Control or 3.4.0.0.3.11 for Attendance System
-
Locate the login page source codeNavigate to the web application directory and find the login page file (commonly index.html, login.jsp, or similar) in the webrootAffected if The login page file exists in the web application directory
-
Search for hardcoded credentials in login sourceOpen the login page source code and search for embedded username or password strings, or examine JavaScript authentication logic for plaintext credentialsAffected if The source code contains any hardcoded username or password values used for authentication bypass
-
Inspect web server configuration filesExamine configuration files in the web application directory for any credentials stored in plain text or hardcoded authentication parametersAffected if Configuration files contain hardcoded credentials or backdoor authentication parameters
-
Test login functionality for bypassAttempt to access restricted areas or system settings using the hardcoded credential found in source code if discoveredAffected if Authentication can be bypassed using a credential found embedded in the source code
A user is affected if their system runs Secom Dr.ID Access Control 3.3.2 or Dr.ID Attendance System 3.4.0.0.3.11 and the login page source code contains a hardcoded credential that permits unauthorized access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove the hard-coded credential from the source code immediately, implement proper dynamic authentication mechanisms, rotate any credentials that may have been exposed, and conduct a thorough code review to identify other hardcoded secrets.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26671 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-26671 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data