# CVE-2026-41317: Frappe Press has an unsafe HTTP method / CSRF-adjacent issue on API secret generation

> An attacker can force a logged-in user to generate API secrets via a GET request, allowing unauthorized modification of account data.

- **Severity:** Medium 6.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-q4wg-jrr8-vpwf

## What is CVE-2026-41317?

CVE-2026-41317 is a medium-severity vulnerability in frappe press, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Press, a Frappe custom app that runs Frappe Cloud, manages infrastructure, subscription, marketplace, and software-as-a-service (SaaS).`press.api.account.create_api_secret` is prone to CSRF-like exploits. This endpoint writes to database and it is also accessible via GET method. The patch in commit 52ea2f2d1b587be0807557e96f025f47897d00fd restricts method to POST.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Frappe Press.

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

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

## Is CVE-2026-41317 being exploited?

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

## Other vulnerabilities in frappe press

- [CVE-2026-41430](https://insights.sbomify.com/CVE-2026-41430/): Press vulnerable to reflected XSS on login redirection (low 1.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41317 is a medium-severity vulnerability in frappe press, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41317 in the wild and no public exploit code.

Affected product: frappe press. 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-41317/ (Markdown: https://insights.sbomify.com/CVE-2026-41317/index.md)
```

## Sources

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

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