{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32789 exists.","fix":"No fix has been published for CVE-2025-32789 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32789 is a low-severity vulnerability in espocrm, published on 16 Apr 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-32789 and fix it if it is affected.\n\nWhat it is: CVE-2025-32789 is a low-severity vulnerability in espocrm, published on 16 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32789 exists.\n\nAffected product: espocrm. 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-32789/ (Markdown: https://insights.sbomify.com/CVE-2025-32789/index.md)","id":"CVE-2025-32789","markdown":"https://insights.sbomify.com/CVE-2025-32789/index.md","name":"CVE-2025-32789","record":{"aliases":["GHSA-3ph3-jcfx-fq53"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"EspoCRM","requires_auth":"low_privilege","summary":"Attackers can infer other users' password hashes by observing sorting results, potentially leading to credential exposure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"espocrm","vendor":"espocrm"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"EspoCRM is an Open Source Customer Relationship Management software. Prior to version 9.0.7, users can be sorted by their password hash. This flaw allows an attacker to make assumptions about the hash values of other users stored in the password column of the user table, based on the results of the sorted list of users. Although unlikely, if an attacker knows the hash value of their password, they can change the password and repeat the sorting until the other user's password hash is fully revealed. This issue is patched in version 9.0.7.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"EspoCRM Allows Potential Disclosure of Sensitive Information in the User Sorting Function","id":"CVE-2025-32789","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Dify Allows Insecure User Role Access Control for APP DSL Exporting","id":"CVE-2025-32790"},"packages":[],"prev":{"headline":"OctoPrint Authenticated Reverse Proxy Page Authentication Bypass","id":"CVE-2025-32788"},"products":["espocrm"],"published":"2025-04-16","related":[{"cvss_score":10,"headline":"Path traversal in n/a","id":"CVE-2014-7985","kev_date_added":null,"published":"2014-10-31"},{"cvss_score":9.1,"headline":"Path traversal in espocrm","id":"CVE-2026-33656","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2022-38843","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2019-14351","kev_date_added":null,"published":"2019-07-28"},{"cvss_score":8.6,"headline":"EspoCRM 5.7.0 \u003c 5.9.0 - Two-Factor Authentication Bypass via Auth Token Reuse Between Accounts with Identical Passwords","id":"CVE-2020-37094","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":8,"headline":"Code injection in n/a","id":"CVE-2022-38844","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":7.2,"headline":"EspoCRM has Admin TemplateManager path traversal that allows arbitrary file read write and delete","id":"CVE-2026-33733","kev_date_added":null,"published":"2026-04-22"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-17","vendors":["espocrm"]},"summary":"Attackers can infer other users' password hashes by observing sorting results, potentially leading to credential exposure.","url":"https://insights.sbomify.com/CVE-2025-32789/"}