# CVE-2024-46413: Server-side request forgery in n/a

> An attacker can exploit an SSRF vulnerability in the Rebuild application's admin controller to access internal resources or bypass security controls.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-x6f8-h6vp-666p

## What is CVE-2024-46413?

CVE-2024-46413 is a medium-severity server-side request forgery vulnerability in n/a, published on 25 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Rebuild v3.7.7 was discovered to contain a Server-Side Request Forgery (SSRF) via the type parameter in the com.rebuild.web.admin.rbstore.RBStoreController#loadDataIndex method.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Getrebuild Rebuild.

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

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

## Is CVE-2024-46413 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-50900](https://insights.sbomify.com/CVE-2025-50900/): Auth bypass in n/a (critical 9.8)
- [CVE-2024-25294](https://insights.sbomify.com/CVE-2024-25294/): Server-side request forgery in n/a (critical 9.1)
- [CVE-2023-2474](https://insights.sbomify.com/CVE-2023-2474/): Rebuild cross-site request forgery (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-46413 is a medium-severity server-side request forgery vulnerability in n/a, published on 25 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-46413 exists.

Affected product: n/a. 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-46413/ (Markdown: https://insights.sbomify.com/CVE-2024-46413/index.md)
```

## Sources

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

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