dbcve.org
Orca HcmApplication · Learningdigital

CVE-2025-1387

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-17
Fix available
A fix is available. Upgrade to 11.0 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
Orca HCM from LEARNING DIGITAL has an Improper Authentication vulnerability, allowing unauthenticated remote attackers to log in to the system as any user.

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

Orca HCM contains an Improper Authentication vulnerability that allows remote, unauthenticated attackers to bypass the login mechanism and gain access to user accounts without valid credentials. Attackers can impersonate any user in the system, potentially obtaining full access to sensitive HR data and system functionalities.

MitigationImmediately restrict network access to the Orca HCM application (e.g., VPN, firewall rules) and implement multi-factor authentication. Contact the vendor for an emergency patch addressing the authentication bypass, and audit system logs for evidence of unauthorized access.

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
Orca HcmApplication
Affected:< 11.0

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 Orca HCM installation
    Locate the Learningdigital Orca HCM application in your environment. Check application inventories, installed software lists, or documentation that tracks enterprise applications.
    Affected if Orca HCM from Learningdigital is present in your environment
  2. Determine installed version
    Locate the version information for your Orca HCM installation. Check the application GUI, about page, installation directory, or configuration files for the version number.
    Affected if The installed version is lower than 11.0 (any version < 11.0)
  3. Verify authentication endpoint exposure
    Identify URLs or endpoints responsible for user authentication (login, session initialization, token validation). Check network configurations, load balancers, or firewall rules to determine if these endpoints are externally accessible.
    Affected if Authentication endpoints are reachable from untrusted networks without proper access controls
  4. Test authentication bypass condition
    If you have a test environment, attempt to access protected resources or user-specific functionality without providing valid credentials. Observe whether the system allows access or impersonation without proper authentication tokens.
    Affected if The system permits access to authenticated features without valid credentials or allows impersonation of arbitrary users

You are affected if Learningdigital Orca HCM version less than 11.0 is installed and its authentication endpoints are accessible, allowing unauthenticated access to the system.

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

Immediately restrict network access to the Orca HCM application (e.g., VPN, firewall rules) and implement multi-factor authentication. Contact the vendor for an emergency patch addressing the authentication bypass, and audit system logs for evidence of unauthorized access.

Recommended fix Moderate confidence

Orca HCM version 11.0 or later

  1. 1. Back up the current Orca HCM installation and database before proceeding with any upgrade.
  2. 2. Obtain Orca HCM version 11.0 or later from the vendor (LEARNING DIGITAL).
  3. 3. Follow the vendor's official upgrade documentation to install version 11.0.
  4. 4. Verify the upgrade was successful by checking the system version information.
  5. 5. Test the authentication mechanism to confirm the vulnerability is remediated.
  6. 6. Monitor system logs for any suspicious authentication activity.
Caveat Review vendor release notes for version 11.0 to check for any breaking changes or migration requirements that may affect your implementation

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

Fix this in Orca Hcm 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-2025-1387 — 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-2025-1387 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