dbcve.org
OrangehrmApplication

CVE-2025-66225

HIGH · 8.8 CVSS v3.1 Published 2025-11-29
Fix available
A fix is available. Upgrade to 5.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
OrangeHRM is a comprehensive human resource management (HRM) system. From version 5.0 to 5.7, the password reset workflow does not enforce that the username submitted in the final reset request matches the account for which the reset process was originally initiated. After obtaining a valid reset link for any account they can receive email for, an attacker can alter the username parameter in the final reset request to target a different user. Because the system accepts the supplied username without verification, the attacker can set a new password for any chosen account, including privileged accounts, resulting in full account takeover. This issue has been patched in version 5.8.

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

OrangeHRM versions 5.0-5.7 contain an IDOR vulnerability in the password reset workflow. An attacker with a valid reset link for one account can modify the username parameter in the final reset request to target a different user. The system fails to verify that the submitted username matches the account for which the reset was initiated, allowing arbitrary password reset for any account including admin accounts.

MitigationUpgrade OrangeHRM to version 5.8 or later where the patch addresses the username verification flaw in the password reset flow.

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
OrangehrmApplication
Affected:>= 5.0, < 5.8

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Determine installed OrangeHRM version
    Log into the OrangeHRM admin dashboard and navigate to Admin > Configuration > System Users, or check the version from the login page footer. Alternatively, inspect the file 'symfony/config/orangehrm.yaml' or the installer configuration file for the version field.
    Affected if The installed version is 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, or 5.7 (versions below 5.8).
  2. Confirm password reset functionality is enabled
    Navigate to Admin > Configuration > Authentication > Password Reset in the admin interface, or inspect the configuration file 'symfony/config/orangehrm_authentication.yaml' to verify that password reset is not disabled.
    Affected if Password reset is enabled and accessible to users.
  3. Check network exposure of password reset endpoint
    Identify if the OrangeHRM instance is publicly accessible or only available within an internal network. Verify that the password reset endpoint '/index.php/auth/resetPassword' or similar is not protected by additional authentication or IP restrictions.
    Affected if The password reset endpoint is reachable from untrusted networks without additional access controls.
  4. Verify no compensating controls exist
    Review web server logs or OrangeHRM audit logs for any password reset activity that shows mismatched usernames between the reset request and the submitted username parameter.
    Affected if No web application firewall, intrusion detection, or additional validation is present to detect username parameter tampering in reset requests.

If the installed OrangeHRM version is 5.0 through 5.7 and the password reset feature is enabled, the environment is affected by this IDOR vulnerability.

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

Upgrade OrangeHRM to version 5.8 or later where the patch addresses the username verification flaw in the password reset flow.

Recommended fix High confidence

5.8

  1. 1. Create a complete backup of the OrangeHRM database and files
  2. 2. Download OrangeHRM version 5.8 from the official OrangeHRM website or GitHub repository
  3. 3. Follow the standard OrangeHRM upgrade procedure for your installation method (composer or manual)
  4. 4. Clear any caches if applicable (var/cache directory)
  5. 5. Verify the upgrade was successful by checking the version in the admin panel
  6. 6. Test the password reset workflow to confirm the vulnerability is patched - ensure username validation is enforced in the final reset request

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

Fix this in Orangehrm Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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