{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92298 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92298 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92298 is a medium-severity vulnerability in EspoCRM, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92298 and fix it if it is affected.\n\nWhat it is: CVE-2026-92298 is a medium-severity vulnerability in EspoCRM, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92298 in the wild and no public exploit code.\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-2026-92298/ (Markdown: https://insights.sbomify.com/CVE-2026-92298/index.md)","id":"CVE-2026-92298","markdown":"https://insights.sbomify.com/CVE-2026-92298/index.md","name":"CVE-2026-92298","record":{"aliases":["GHSA-2p88-mrx2-p76v"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"CRM software","requires_auth":"none","summary":"Remote attackers can guess weak tokens to access event details and modify invitation statuses in EspoCRM.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"EspoCRM through 10.0.8 uses PHP's rand() function to generate tokens for lead-capture opt-in, event invitation, and campaign URLs instead of a cryptographically secure generator. Remote unauthenticated attackers can guess these roughly 31-bit tokens to confirm opt-ins, accept or decline event invitations on behalf of other contacts, and access event details.","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":"EspoCRM through 10.0.8 Weak Token Generation via rand()","id":"CVE-2026-92298","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"@jitsi/electron-sdk before 10.0.5 Unauthorized Screen Capture","id":"CVE-2026-92299"},"packages":[],"prev":{"headline":"Lemonldap::NG::Portal versions from 2.23.0 before 2.23.4 for Perl allow a PKCE bypass for public Relying Parties in \"PKCE or secret\" mode be","id":"CVE-2026-92289"},"products":["EspoCRM"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["EspoCRM"]},"summary":"Remote attackers can guess weak tokens to access event details and modify invitation statuses in EspoCRM.","url":"https://insights.sbomify.com/CVE-2026-92298/"}