CVE-2026-62315

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 20, 2026

Last Modified

August 20, 2026

Advisory Details (3)

Auto-updated Aug 20, 2026
Patch available. Sources: github, github_pr, github_commit.
github_commit

commit 2a04fae9353c (frappe/frappe)

Fix landed in frappe/frappe commit 2a04fae9353c — awaiting tagged release

https://github.com/frappe/frappe/commit/2a04fae9353c02f0a9ce9f40f92c1eba6765c77b
github_pr

fix(client): add proper checks to client.py endpoints.

Fix merged in frappe/frappe PR #38951 on 2026-06-26 — awaiting tagged release

https://github.com/frappe/frappe/pull/38951
github Patch Available

Mass assignment in client endpoint · Advisory · frappe/frappe · GitHub

https://github.com/frappe/frappe/security/advisories/GHSA-2c6h-wv85-fxvj

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 15:25 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 16:10 UTCEG score recompute
  4. 2026-08-23 05:22 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 06:10 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-20 19:18 UTCEG score recompute
  9. 2026-08-20 19:12 UTCEG score recompute
  10. 2026-08-20 18:32 UTCEG score recompute
  11. 2026-08-20 18:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62315?
CVE-2026-62315 is a high vulnerability published on August 20, 2026. 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…
When was CVE-2026-62315 disclosed?
CVE-2026-62315 was first published in the National Vulnerability Database on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62315 actively exploited?
CVE-2026-62315 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.1% of all scored CVEs.
What is the CVSS score of CVE-2026-62315?
CVE-2026-62315 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-62315?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62315, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62315

Explore →

Is Your Infrastructure Affected by CVE-2026-62315?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs