# CVE-2025-59421: Press vulnerable to email flooding to users due to lack of validation and rate limits

> Attackers can flood user inboxes with duplicate invites due to missing validation and rate limits in the Frappe Press application.

- **Severity:** Low 2.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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:** 18 Sep 2025
- **Updated:** 19 Sep 2025
- **Also known as:** GHSA-68qm-vp8f-rpr3

## What is CVE-2025-59421?

CVE-2025-59421 is a low-severity denial of service vulnerability in frappe press, published on 18 Sep 2025. 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). A bad actor can flood the inbox of a user by repeatedly sending invites (duplicate). The issue is fixed in commit 83c3fc7676c5dbbe1fd5092d21d95a10c7b48615.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2025-59421?


## How do I fix CVE-2025-59421?

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

## Is CVE-2025-59421 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59421 and fix it if it is affected.

What it is: CVE-2025-59421 is a low-severity denial of service vulnerability in frappe press, published on 18 Sep 2025. 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-2025-59421 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-2025-59421/ (Markdown: https://insights.sbomify.com/CVE-2025-59421/index.md)
```

## Sources

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

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