dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-30013

MEDIUM · 6.7 CVSS v3.1 Published 2025-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SAP ERP BW Business Content contains OS command injection vulnerabilities in certain function modules. When these modules execute with elevated privileges, they improperly handle user-supplied input, allowing attackers to inject and execute arbitrary OS commands on the underlying system.

MitigationApply SAP security patches for CVE-2025-30013 when available. Until then, restrict access to vulnerable function modules, implement strict input validation on all user-supplied parameters, and review privileged user permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SAP ERP BW Business Content installation
    Check the SAP system landscape for SAP ERP BW (Business Warehouse) components and Business Content packages installed. Use transaction code SE16 or SM37 to query table SAPC_COMPONENTS or check installed software components.
    Affected if SAP ERP BW with Business Content is installed on the system
  2. Identify Business Content function modules
    Use SAP transaction code SE37 (Function Builder) to search for function modules within the BW-related function groups. Look for modules that perform OS-level operations or system command execution, particularly those handling external program execution or shell commands.
    Affected if Business Content function modules that execute OS commands are present in the system
  3. Verify elevated privilege configuration
    Check the authorization profiles and roles assigned to the function modules. Use transaction code SUIM (User Information System) or check the user execution context. Determine if the modules run under privileged accounts (e.g., SAP*, DDIC, or service accounts with OS-level access).
    Affected if The function modules execute under user accounts with elevated or privileged OS-level permissions
  4. Check for external input handling in BW modules
    Review the ABAP source code of identified function modules for parameters that accept user input and are passed to operating system command execution routines (e.g., SUBMIT, CALL 'SYSTEM', CL_BCS=>CREATE). Use transaction code SE80 or SE37 to inspect module logic.
    Affected if User-supplied parameters are directly or indirectly passed to OS command execution without proper validation
  5. Audit access to vulnerable modules
    Use transaction code SUIM to review which users have authorization to execute the identified BW function modules. Check for excessive or unnecessary permissions granted to standard or business users.
    Affected if Multiple users or roles have direct access to function modules that perform OS command execution

The environment is affected if SAP ERP BW Business Content is installed and vulnerable function modules that execute OS commands are active and accessible under elevated privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security patches for CVE-2025-30013 when available. Until then, restrict access to vulnerable function modules, implement strict input validation on all user-supplied parameters, and review privileged user permissions.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30013 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data