# CVE-2025-30013: Code Injection vulnerability in SAP ERP BW Business Content

> Attackers can inject arbitrary OS commands via vulnerable function modules in SAP ERP BW Business Content, leading to code execution on the underlying system.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-55pg-m6v3-xwh9

## What is CVE-2025-30013?

CVE-2025-30013 is a medium-severity command injection vulnerability in SAP_SE SAP ERP BW Business Content, published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SAP ERP BW Business Content is vulnerable to OS Command Injection through certain function modules. These function modules, when executed with elevated privileges, improperly handle user input, allowing attacker to inject arbitrary OS commands. This vulnerability allows the execution of unintended commands on the underlying system, posing a significant security risk to the confidentiality, integrity and availability of the application.

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

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


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

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

## Is CVE-2025-30013 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30013 is a medium-severity command injection vulnerability in SAP_SE SAP ERP BW Business Content, published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30013 in the wild and no public exploit code.

Affected product: SAP_SE SAP ERP BW Business Content. 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-30013/ (Markdown: https://insights.sbomify.com/CVE-2025-30013/index.md)
```

## Sources

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

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