# CVE-2025-27430: Server Side Request Forgery (SSRF) in SAP CRM and SAP S/4 HANA (Interaction Center)

> An attacker with low privileges can exploit an SSRF vulnerability in SAP CRM and S/4HANA to access restricted internal network information.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 11 Mar 2025
- **Also known as:** GHSA-535h-62c3-g4j6

## What is CVE-2025-27430?

CVE-2025-27430 is a low-severity server-side request forgery vulnerability in SAP_SE SAP CRM and SAP S/4HANA (Interaction Center), published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Under certain conditions, an SSRF vulnerability in SAP CRM and SAP S/4HANA (Interaction Center) allows an attacker with low privileges to access restricted information. This flaw enables the attacker to send requests to internal network resources, thereby compromising the application's confidentiality. There is no impact on integrity or availability

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

## Which versions are affected by CVE-2025-27430?


## How do I fix CVE-2025-27430?

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

## Is CVE-2025-27430 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27430 and fix it if it is affected.

What it is: CVE-2025-27430 is a low-severity server-side request forgery vulnerability in SAP_SE SAP CRM and SAP S/4HANA (Interaction Center), published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27430 in the wild and no public exploit code.

Affected product: SAP_SE SAP CRM and SAP S/4HANA (Interaction Center). 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-2025-27430/ (Markdown: https://insights.sbomify.com/CVE-2025-27430/index.md)
```

## Sources

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

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