# CVE-2025-42887: Code Injection vulnerability in SAP Solution Manager

> An authenticated attacker can inject malicious code via remote function modules in SAP Solution Manager, gaining full system control.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-cqr5-w9rg-4vm5

## What is CVE-2025-42887?

CVE-2025-42887 is a critical code injection vulnerability in SAP_SE SAP Solution Manager, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to missing input sanitation, SAP Solution Manager allows an authenticated attacker to insert malicious code when calling a remote-enabled function module. This could provide the attacker with full control of the system hence leading to high impact on confidentiality, integrity and availability of the system.

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

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


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

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

## Is CVE-2025-42887 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42887 is a critical code injection vulnerability in SAP_SE SAP Solution Manager, published on 11 Nov 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-42887 in the wild and no public exploit code.

Affected product: SAP_SE SAP Solution Manager. 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-42887/ (Markdown: https://insights.sbomify.com/CVE-2025-42887/index.md)
```

## Sources

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

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