# CVE-2026-47422: Frappe: Unrestricted API access to save_report

> Attackers can access the save_report endpoint without permission checks, allowing unauthorized modification of reports in Frappe applications.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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:** 10 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-w8g7-j846-j248

## What is CVE-2026-47422?

CVE-2026-47422 is a medium-severity missing authorization vulnerability in frappe, published on 10 Jul 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. Prior to 15.107.5 and 16.18.2, an endpoint in reportview lacked appropriate permission checks and that has since been fixed. This vulnerability is fixed in 15.107.5 and 16.18.2.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-47422 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47422 is a medium-severity missing authorization vulnerability in frappe, published on 10 Jul 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-47422 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-47422/ (Markdown: https://insights.sbomify.com/CVE-2026-47422/index.md)
```

## Sources

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

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