dbcve.org
Workforce AccessApplication · Hypr

CVE-2023-5097

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 8.7 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Improper Input Validation vulnerability in HYPR Workforce Access on Windows allows Path Traversal.This issue affects Workforce Access: before 8.7.

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

HYPR Workforce Access on Windows contains an improper input validation vulnerability that allows path traversal. Attackers can potentially access files outside the web root folder by manipulating file path inputs with directory traversal sequences (e.g., ../../). This affects all versions before 8.7.

MitigationUpgrade HYPR Workforce Access to version 8.7 or later to remediate this vulnerability. Additionally, implement proper input validation and sanitization for file path parameters to prevent path traversal attacks.

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
Workforce AccessApplication
Affected:< 8.7

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

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

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 if HYPR Workforce Access is installed
    Check for HYPR Workforce Access installation directory, typically found under C:\Program Files\HYPR or C:\Program Files (x86)\HYPR. Also check Windows Services for 'HYPR Workforce Access' service.
    Affected if The software is not present on the system.
  2. Determine installed version of HYPR Workforce Access
    Locate the installation directory and look for version information in the executable or a version file. Common locations: right-click the main executable file, select Properties, then view the Details tab for File Version. Alternatively, check the Windows Programs and Features list.
    Affected if The installed version is lower than 8.7.
  3. Verify web interface is accessible
    Check if the HYPR Workforce Access web service is running and exposed. Look for IIS configuration or the embedded web server port (typically ports 8080, 8443, or 443). Review Windows Services to confirm the HYPR service is running.
    Affected if The web service is running and accessible to users or attackers.
  4. Check for suspicious file access patterns in logs
    Examine HYPR Workforce Access logs, Windows IIS logs, or web server access logs for patterns containing directory traversal sequences such as ../, ..\, or absolute path attempts (e.g., /etc/passwd, C:\Windows\). Review logs in the installation directory under a logs or data folder.
    Affected if Log entries contain directory traversal sequences in file path parameters.

A system is affected if HYPR Workforce Access is installed with a version lower than 8.7 and the web interface is accessible, allowing external input to reach file path parameters.

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 8.7 or later
Fixed in 8.7
Interim mitigation

Upgrade HYPR Workforce Access to version 8.7 or later to remediate this vulnerability. Additionally, implement proper input validation and sanitization for file path parameters to prevent path traversal attacks.

Recommended fix Moderate confidence

8.7

  1. 1. Backup your current HYPR Workforce Access installation and configuration data
  2. 2. Download the latest version 8.7 of HYPR Workforce Access from the official HYPR website (www.hypr.com) or your authorized distribution channel
  3. 3. Stop the HYPR Workforce Access service on your Windows server
  4. 4. Install version 8.7 by running the installer with appropriate administrative privileges
  5. 5. Verify the installation completed successfully
  6. 6. Start the HYPR Workforce Access service
  7. 7. Confirm the service is running and accessible
  8. 8. Validate that the path traversal vulnerability is no longer present by testing file access controls

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

Fix this in Workforce Access Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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