# CVE-2024-52598: 2FAuth vulnerable to Server Side Request Forgery + URI validation bypass in 2fauth /api/v1/twofaccounts/preview

> Attackers can exploit SSRF and URI validation bypass in 2FAuth to retrieve arbitrary internal resources via the preview endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2024
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-xwxc-w7v3-2p4j

## What is CVE-2024-52598?

CVE-2024-52598 is a high-severity server-side request forgery vulnerability in Bubka 2FAuth, published on 20 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

2FAuth is a web app to manage Two-Factor Authentication (2FA) accounts and generate their security codes. Two interconnected vulnerabilities exist in version 5.4.1 a SSRF and URI validation bypass issue. The endpoint at POST /api/v1/twofaccounts/preview allows setting a remote URI to retrieve the image of a 2fa site. By abusing this functionality, it is possible to force the application to make a GET request to an arbitrary URL, whose content will be stored in an image file in the server if it looks like an image. Additionally, the library does some basic validation on the URI, attempting to filter our URIs which do not have an image extension. However, this can be easily bypassed by appending the string `#.svg` to the URI. The combination of these two issues allows an attacker to retrieve URIs accessible from the application, as long as their content type is text based. If not, the request is still sent, but the response is not reflected to the attacker. Version 5.4.1 fixes the issues.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: 2fauth 2fauth.

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

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

## Is CVE-2024-52598 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52598 exists.

## Other vulnerabilities in Bubka 2FAuth

- [CVE-2026-32133](https://insights.sbomify.com/CVE-2026-32133/): 2FAuth has Blind SSRF in image parameter allows internal network access and more (high 7.8)
- [CVE-2025-45731](https://insights.sbomify.com/CVE-2025-45731/): Race condition in n/a (medium 6.5)
- [CVE-2024-52597](https://insights.sbomify.com/CVE-2024-52597/): 2FAuth vulnerable to stored cross-site scripting via SVG upload and direct access render (medium 6.1)
- [CVE-2023-36816](https://insights.sbomify.com/CVE-2023-36816/): Cross-Site Scripting (XSS) at Account creation in 2FAuth (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52598 is a high-severity server-side request forgery vulnerability in Bubka 2FAuth, published on 20 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52598 exists.

Affected product: Bubka 2FAuth. 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-52598/ (Markdown: https://insights.sbomify.com/CVE-2024-52598/index.md)
```

## Sources

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

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