CVE-2026-39346
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 · uneditedOrangeHRM is a comprehensive human resource management (HRM) system. From 5.0 to 5.8, OrangeHRM Open Source allowed authenticated users to bypass disabled-module access controls via URL-encoded request paths and access functionality of modules disabled by an administrator. This vulnerability is fixed in 5.8.1.
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 confidenceOrangeHRM Open Source versions 5.0 through 5.8 contained an access control bypass vulnerability where authenticated users could circumvent module restrictions disabled by administrators through URL-encoded request paths. The vulnerability allowed low-privilege authenticated users to access functionality of modules that administrators had explicitly disabled.
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>= 5.0, < 5.8.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed OrangeHRM versionLocate the version information in the OrangeHRM installation, typically found in the system info page, configuration file, or about section of the web interfaceAffected if The version is 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, or 5.8.0 (any version >= 5.0 and < 5.8.1)
-
Determine if any modules have been disabled by an administratorReview the module configuration or permissions settings in the OrangeHRM admin panel to identify which modules are currently disabledAffected if Any module has been disabled by an administrator - the bypass only affects disabled modules
-
Verify URL-encoded path handlingIf you have access to a test environment, attempt to access a disabled module using a URL-encoded request path (e.g., /index.php/%61dmin/moduleName) to see if the restriction is bypassedAffected if The URL-encoded request successfully returns content or functionality from a module that is marked as disabled in the admin panel
-
Review access logs for suspicious patternsExamine OrangeHRM access logs for requests containing URL-encoded paths to admin or module endpoints, particularly from non-administrator accountsAffected if Logs show authenticated users accessing administrator pages or disabled modules via encoded URL paths
Your environment is affected if OrangeHRM Open Source version is 5.0 through 5.8.0 and you have disabled modules that could be bypassed via URL-encoded request paths.
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.
dbcve · scoped5.8.1
Upgrade OrangeHRM to version 5.8.1 or later which contains the patch for this access control bypass. Verify that disabled modules remain inaccessible after upgrading.
OrangeHRM 5.8.1 or later
- 1. Back up the current OrangeHRM installation and database before starting the upgrade process
- 2. Download OrangeHRM version 5.8.1 or later from the official OrangeHRM website or repository
- 3. Follow OrangeHRM's standard upgrade procedure to update from your current version (>=5.0) to 5.8.1
- 4. After upgrade, verify that modules disabled by an administrator cannot be accessed via URL manipulation
- 5. Test that URL-encoded request paths no longer bypass disabled-module access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39346 — 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-2026-39346 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