dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-25244

MEDIUM · 5.7 CVSS v3.1 Published 2025-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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 Business Warehouse (Process Chains) allows an attacker to manipulate the process execution due to missing authorization check. An attacker with display authorization for the process chain object could set one or all processes to be skipped. This means corresponding activities, such as data loading, activation, or deletion, will not be executed as initially modeled. This could lead to unexpected results in business reporting leading to a significant impact on integrity. However, there is no impact on confidentiality or availability.

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 · high confidence

SAP Business Warehouse Process Chains lacks proper authorization checks, allowing users with only display authorization to modify process execution settings. An attacker can set processes to be skipped, preventing data loading, activation, or deletion activities from running as designed, leading to inaccurate business reporting.

MitigationImplement proper authorization checks in SAP BW Process Chain transactions (RSPC) using authorization objects (e.g., S_RS_PC) to restrict modification of process execution settings to users with appropriate change privileges, not just display access.

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Identify SAP BW version
    Execute transaction SM37 or log into SAP GUI and check system information via System > Status. Look for SAP_BW component version in system details.
    Affected if The installed SAP BW version falls within unpatched releases and the system has not applied the relevant security note for CVE-2025-25244.
  2. Verify RSPC transaction authorization configuration
    Run transaction SU53 immediately after attempting to access RSPC (Process Chain maintenance) with display-only credentials to check for missing authorization objects.
    Affected if Users with only display-level authorizations (S_RS_PC with actvt = 03) can access modification functions in transaction RSPC.
  3. Inspect Process Chain modification permissions
    In RSPC, attempt to edit a process chain (e.g., change 'Execute' to 'Skip' or modify variant settings) using a user account that should have only display access. Check if changes can be saved.
    Affected if A user lacking change privileges (actvt = 02) can successfully modify process execution settings such as process skipping, variant overrides, or scheduling parameters.
  4. Review S_RS_PC authorization object assignments
    Use transaction SUIM to search for users assigned S_RS_PC. Check authorization field ACTVT values assigned to affected user roles.
    Affected if Roles or users possess S_RS_PC authorization without restricted ACTVT values, allowing modification operations despite intended display-only access.
  5. Examine Process Chain execution logs
    In RSPC, review recent process chain executions via the log display. Look for chains where processes were skipped or had altered execution behavior that was not initiated by an authorized administrator.
    Affected if Process chains show skipped processes or altered execution modes that were not authorized by users with proper change privileges.

A user with only display authorization in S_RS_PC can modify process chain execution settings in transaction RSPC, indicating the environment is vulnerable to this authorization bypass.

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

Implement proper authorization checks in SAP BW Process Chain transactions (RSPC) using authorization objects (e.g., S_RS_PC) to restrict modification of process execution settings to users with appropriate change privileges, not just display access.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25244 — 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-25244 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