AI Threat Alert
CVE-2026-92298
MEDIUMEspoCRM 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...
Full CISO analysis pending enrichment.
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| EspoCRM | — | — | No patch |
Do you use EspoCRM? You're affected.
How severe is it?
What is the attack surface?
What should I do?
No patch available
Monitor for updates. Consider compensating controls or temporary mitigations.
Which compliance frameworks are affected?
Compliance analysis pending. Sign in for full compliance mapping when available.
Frequently Asked Questions
What is CVE-2026-92298?
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.
Is CVE-2026-92298 actively exploited?
No confirmed active exploitation of CVE-2026-92298 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-92298?
No patch is currently available. Monitor vendor advisories for updates.
What is the CVSS score for CVE-2026-92298?
CVE-2026-92298 has a CVSS v3.1 base score of 4.8 (MEDIUM). The EPSS exploitation probability is 0.32%.
What are the technical details?
Original Advisory
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.
Weaknesses (CWE)
CWE-338 — Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG): The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
- [Implementation] Use functions or hardware which use a hardware-based random number generation for all crypto. This is the recommended solution. Use CyptGenRandom on Windows, or hw_rand() on Linux.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N References
- gist.github.com/kazisabu/9e3109aab24245fde19b88f53f965e93 technical-description
- github.com/espocrm/espocrm product
- github.com/espocrm/espocrm/blob/10.0.8/application/Espo/Core/Utils/Util.php technical-description
- github.com/espocrm/espocrm/blob/10.0.8/application/Espo/Repositories/UniqueId.php technical-description
- github.com/espocrm/espocrm/commit/8e5555c1ee0ed1e92a9ad54e62f735ac2c4051a1 patch
- vulncheck.com/advisories/espocrm-through-10.0.8-weak-token-generation-via-rand third-party-advisory