dbcve.org
SafeApplication · Hidglobal

CVE-2023-2904

HIGH · 7.3 CVSS v3.1 Published 2023-06-07
Fix available
A fix is available. Upgrade to after 5.11.3 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable

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
The External Visitor Manager portal of HID’s SAFE versions 5.8.0 through 5.11.3 are vulnerable to manipulation within web fields in the application programmable interface (API). An attacker could log in using account credentials available through a request generated by an internal user and then manipulate the visitor-id within the web API to access the personal data of other users. There is no limit on the number of requests that can be made to the HID SAFE Web Server, so an attacker could also exploit this vulnerability to create a denial-of-service condition.

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 confidence

The HID SAFE Visitor Manager portal versions 5.8.0-5.11.3 contains an Insecure Direct Object Reference (IDOR) vulnerability in its web API. An authenticated attacker can manipulate the visitor-id parameter in API requests to access personal data of other visitors. Additionally, the lack of rate limiting on the API allows unlimited requests, enabling denial-of-service conditions.

MitigationImplement proper authorization checks to ensure users can only access their own visitor records, and add rate limiting/throttling to API endpoints to prevent abuse and DoS conditions.

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
SafeApplication
Affected:>= 5.8.0, <= 5.11.3

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/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 installed HID SAFE Visitor Manager version
    Locate the product version through the administration console, system information page, or version display in the portal footer. Check installation directories for version manifest files.
    Affected if Installed version is 5.8.0, 5.9.x, 5.10.x, 5.11.0, 5.11.1, 5.11.2, or 5.11.3.
  2. Verify API endpoint exposure
    Confirm the web API endpoints are accessible by accessing the API base URL (typically /api/ or /visitorapi/) through the web interface or direct HTTP request.
    Affected if API endpoints are exposed and accessible without additional network segmentation.
  3. Check for rate limiting configuration
    Review the API gateway or web server configuration files (such as nginx.conf, web.config, or application config) for rate limiting, throttling, or request limiting rules applied to the visitor API endpoints.
    Affected if No rate limiting or throttling rules are configured for the API endpoints, or the configuration allows unlimited requests per IP or session.
  4. Confirm authentication is enabled
    Verify that the portal requires authentication for access. Attempt to access visitor data endpoints without providing valid credentials.
    Affected if Authentication is not enforced on the API endpoints, allowing unauthenticated access to visitor records.

The environment is affected if HID SAFE Visitor Manager version 5.8.0 through 5.11.3 is installed and the web API is accessible without proper rate limiting and authorization controls.

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.

From vendor data
Upgrade available Upgrade to a release after 5.11.3
Interim mitigation

Implement proper authorization checks to ensure users can only access their own visitor records, and add rate limiting/throttling to API endpoints to prevent abuse and DoS conditions.

Fix this in Safe Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2904 — 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-2023-2904 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