# CVE-2024-58258: Server-side request forgery in SugarCRM

> An attacker can exploit SSRF in the API module to potentially execute code or access internal resources.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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:** 13 Jul 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-828p-92r7-xw6x

## What is CVE-2024-58258?

CVE-2024-58258 is a high-severity server-side request forgery vulnerability in SugarCRM, published on 13 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SugarCRM before 13.0.4 and 14.x before 14.0.1 allows SSRF in the API module because a limited type of code injection can occur.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2024-58258 being exploited?

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

Public exploit code:

- Proof‑of‑concept for CVE‑2024‑58258, a SugarCRM (<13.0.4 / <14.0.1) flaw where user input is parsed as LESS in /css/preview, allowing unauthenticated SSRF or local file access. (github_poc): https://github.com/Web3-Serializer/CVE-2024-58258
- SugarCRM 14.0.0 - SSRF/Code Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-58258 is a high-severity server-side request forgery vulnerability in SugarCRM, published on 13 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-2024-58258 in the wild and no public exploit code.

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

## Sources

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

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