{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-66225 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-66225 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66225 is a high-severity vulnerability in orangehrm, published on 29 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66225 and fix it if it is affected.\n\nWhat it is: CVE-2025-66225 is a high-severity vulnerability in orangehrm, published on 29 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-66225 in the wild and no public exploit code.\n\nAffected product: orangehrm. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-66225/ (Markdown: https://insights.sbomify.com/CVE-2025-66225/index.md)","id":"CVE-2025-66225","markdown":"https://insights.sbomify.com/CVE-2025-66225/index.md","name":"CVE-2025-66225","record":{"aliases":["GHSA-5ghw-9775-v263"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"HRM system","requires_auth":"low_privilege","summary":"Attackers can hijack any user account, including admins, by manipulating the username parameter during the password reset process.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"orangehrm","vendor":"orangehrm"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-640","name":"Weak Password Recovery Mechanism for Forgotten Password"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"OrangeHRM is Vulnerable to Account Takeover Through Unvalidated Username in Password Reset Workflow","id":"CVE-2025-66225","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Not used","id":"CVE-2025-66228"},"packages":[],"prev":{"headline":"OrangeHRM is Vulnerable to Code Execution Through Arbitrary File Write from Sendmail Parameter Injection","id":"CVE-2025-66224"},"products":["orangehrm"],"published":"2025-11-29","related":[{"cvss_score":9.3,"headline":"Other in n/a","id":"CVE-2007-1193","kev_date_added":null,"published":"2007-03-02"},{"cvss_score":9,"headline":"OrangeHRM is Vulnerable to Code Execution Through Arbitrary File Write from Sendmail Parameter Injection","id":"CVE-2025-66224","kev_date_added":null,"published":"2025-11-29"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2019-12839","kev_date_added":null,"published":"2019-06-15"},{"cvss_score":8.7,"headline":"OrangeHRM is Vulnerable to Persistent Session Access Due to Missing Invalidation After User Disable and Password Change","id":"CVE-2025-66289","kev_date_added":null,"published":"2025-11-29"},{"cvss_score":8.1,"headline":"SQL injection in n/a","id":"CVE-2024-36428","kev_date_added":null,"published":"2024-05-27"},{"cvss_score":8.1,"headline":"SQL injection in n/a","id":"CVE-2020-29437","kev_date_added":null,"published":"2021-01-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-01","vendors":["orangehrm"]},"summary":"Attackers can hijack any user account, including admins, by manipulating the username parameter during the password reset process.","url":"https://insights.sbomify.com/CVE-2025-66225/"}