EspoCRM through 10.0.8 Weak Token Generation via rand()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| EspoCRM | EspoCRM | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Espocrm | Espocrm |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.430% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | EspoCRM through 10.0.8 Weak Token Generation via rand() | |
| First Time appeared |
Espocrm
Espocrm espocrm |
|
| Weaknesses | CWE-338 | |
| CPEs | cpe:2.3:a:espocrm:espocrm:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Espocrm
Espocrm espocrm |
|
| References |
|
|
| Metrics |
cvssV3_1
|