# CVE-2025-53545: Press has a potential 2FA bypass

> Attackers can bypass two-factor authentication on Frappe Cloud due to missing server-side validation, potentially taking over user accounts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-fwfh-vhjg-45q4

## What is CVE-2025-53545?

CVE-2025-53545 is a medium-severity authentication bypass vulnerability in frappe press, published on 8 Jul 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). Users can circumvent 2FA login for users due to a lack of server side validation for the same. This vulnerability is fixed in commit ddb439f8eb1816010f2ef653a908648b71f9bba8.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2025-53545 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53545 is a medium-severity authentication bypass vulnerability in frappe press, published on 8 Jul 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-53545 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-53545/ (Markdown: https://insights.sbomify.com/CVE-2025-53545/index.md)
```

## Sources

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

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