dbcve.org
Dr.id Attendance SystemApplication · Secom

CVE-2024-7732

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 3.5.0.0.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Dr.ID Access Control System from SECOM does not properly validate a specific page parameter, allowing unauthenticated remote attackers to inject SQL commands to read, modify, and delete database contents.

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 · moderate confidence

Dr.ID Access Control System from SECOM contains an unauthenticated SQL injection vulnerability in a specific page parameter that lacks proper input validation. This allows remote attackers to execute arbitrary SQL commands, enabling full database compromise including read, write, and delete operations.

MitigationImplement parameterized queries or prepared statements for all database interactions, apply vendor-provided patches, and consider deploying a WAF with SQL injection rules as a temporary mitigation until the patch is applied.

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
Dr.id Attendance SystemApplication
Affected:< 3.5.0.0.0.5

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Dr.ID version
    Locate the installed version of the Dr.ID Attendance System through the web admin interface (typically found in About or System Info pages), or check the application binaries/install directory for version files
    Affected if Installed version is lower than 3.5.0.0.0.5
  2. Determine network exposure
    Check if the Dr.ID web interface is accessible from untrusted networks or the internet without authentication requirements
    Affected if The application is exposed to unauthenticated network access
  3. Inspect HTTP access logs
    Review web server and application logs for suspicious SQL syntax in HTTP request parameters, especially on unknown or unexpected pages
    Affected if Log entries show SQL-like characters (such as quotes, UNION, SELECT, or semicolons) in page parameters without proper sanitization
  4. Verify database user privileges
    Examine the database configuration to determine what privileges the application database user has
    Affected if The application database user has elevated privileges that could allow unauthorized data access or modification

The environment is affected if the installed Dr.ID Attendance System version is below 3.5.0.0.0.5 and the web interface is accessible to unauthenticated attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.5.0.0.0.5 or later
Fixed in 3.5.0.0.0.5
Interim mitigation

Implement parameterized queries or prepared statements for all database interactions, apply vendor-provided patches, and consider deploying a WAF with SQL injection rules as a temporary mitigation until the patch is applied.

Recommended fix Moderate confidence

3.5.0.0.0.5

  1. Contact SECOM support or visit the official SECOM Dr.ID support portal to obtain version 3.5.0.0.0.5 or later
  2. Download the updated Dr.id Attendance System version 3.5.0.0.0.5
  3. Back up the current database and configuration files before upgrading
  4. Install the updated version following SECOM's documented upgrade procedure
  5. Verify the SQL injection vulnerability is resolved by testing the affected parameter
  6. Confirm normal attendance system functionality after the upgrade
Caveat Review SECOM release notes for version 3.5.0.0.0.5 for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dr.id Attendance System Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7732 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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