# CVE-2024-50356: Press has a potential 2FA bypass

> Attackers with mail inbox access can reset passwords for users with 2FA enabled, potentially leading to account takeover despite 2FA restrictions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2024
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-g7mf-rm73-r7g9

## What is CVE-2024-50356?

CVE-2024-50356 is an authentication bypass vulnerability in frappe press, published on 31 Oct 2024. 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). The password could be reset by anyone who have access to the mail inbox circumventing the 2FA. Even though they wouldn't be able to login by bypassing the 2FA. Only users who have enabled 2FA are affected. Commit ba0007c28ac814260f836849bc07d29beea7deb6 patches this bug.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2024-50356?


## How do I fix CVE-2024-50356?

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

## Is CVE-2024-50356 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50356 and fix it if it is affected.

What it is: CVE-2024-50356 is an authentication bypass vulnerability in frappe press, published on 31 Oct 2024. 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-2024-50356 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-2024-50356/ (Markdown: https://insights.sbomify.com/CVE-2024-50356/index.md)
```

## Sources

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

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