# CVE-2026-62315: Frappe: Mass assignment via set_value

> Authenticated attackers can bypass field restrictions to modify protected data via mass assignment in the Frappe framework.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-2c6h-wv85-fxvj

## What is CVE-2026-62315?

CVE-2026-62315 is a high-severity missing authorization vulnerability in frappe, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

## Which versions are affected by CVE-2026-62315?


## How do I fix CVE-2026-62315?

No fix has been published for CVE-2026-62315 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62315 being exploited?

There is no known exploitation of CVE-2026-62315 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62315 and fix it if it is affected.

What it is: CVE-2026-62315 is a high-severity missing authorization vulnerability in frappe, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62315 in the wild and no public exploit code.

Affected product: frappe. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62315/ (Markdown: https://insights.sbomify.com/CVE-2026-62315/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62315
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62315
- OSV: https://osv.dev/vulnerability/CVE-2026-62315

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62315/
Summaries are generated and may contain mistakes; the official description above is the record.