EspoCRM 4.0.0 before 10.0.7 Field-Level Security Bypass via Note Read Endpoint
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.223% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | EspoCRM 4.0.0 before 10.0.7 contains an access control vulnerability that allows authenticated users to read audited field values restricted by field-level security by fetching individual stream notes. Users with stream access to a parent record can request GET /Note/{id}, which skips the NoteAccessControl filter, and recover data.attributes.was and became values of restricted fields. | |
| Title | EspoCRM 4.0.0 before 10.0.7 Field-Level Security Bypass via Note Read Endpoint | |
| First Time appeared |
Espocrm
Espocrm espocrm |
|
| Weaknesses | CWE-200 | |
| CPEs | cpe:2.3:a:espocrm:espocrm:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Espocrm
Espocrm espocrm |
|
| References |
| |
| Metrics |
cvssV3_1
|