Frappe: Mass assignment via set_value
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| frappe | frappe | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Frappe | Frappe |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.487% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Frappe
Frappe frappe |
|
| Vendors & Products |
Frappe
Frappe frappe |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Frappe is a full-stack web application framework. In version 16.31.0 and earlier, frappe.client.set_value in frappe/client.py checks a dictionary supplied through the fieldname parameter against forbidden standard and child-table fields before parsing the dictionary into individual field names. An authenticated caller can exploit this type confusion to mass-assign protected fields through the client endpoint. No released fixed version is available as of this review. | |
| Title | Frappe: Mass assignment via set_value | |
| Weaknesses | CWE-915 | |
| References |
| |
| Metrics |
cvssV4_0
|