EspoCRM: Mass email template renderer leaks restricted record fields
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 | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Espocrm | Espocrm |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.231% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Espocrm
Espocrm espocrm |
|
| Vendors & Products |
Espocrm
Espocrm espocrm |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | EspoCRM is an open source customer relationship management application. Prior to 10.0.3, a user with email-template edit access and mass-email sending access can reference restricted record fields in a template because the renderer stops filtering those fields when per-user ACL application is disabled. The same behavior affects group email auto-replies when a regular user can edit the selected template, even though an administrator controls the group email. Rendered messages can disclose restricted user fields. This issue is fixed in version 10.0.3. | |
| Title | EspoCRM: Mass email template renderer leaks restricted record fields | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|