# CVE-2025-24872: Missing Authorization check in SAP ABAP Platform (ABAP Build Framework)

> An authenticated attacker can bypass authorization checks to view details of a specific transaction in the SAP ABAP Build Framework.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 Feb 2025
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-x2gh-hgcj-q83q

## What is CVE-2025-24872?

CVE-2025-24872 is a medium-severity missing authorization vulnerability in SAP_SE SAP ABAP Platform (ABAP Build Framework), published on 11 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The ABAP Build Framework in SAP ABAP Platform allows an authenticated attacker to gain unauthorized access to a specific transaction. By executing the add-on build functionality within the ABAP Build Framework, an attacker could call the transaction and view its details. This has a limited impact on the confidentiality of the application with no effect on the integrity and availability of the application.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-24872 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24872 is a medium-severity missing authorization vulnerability in SAP_SE SAP ABAP Platform (ABAP Build Framework), published on 11 Feb 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-24872 in the wild and no public exploit code.

Affected product: SAP_SE SAP ABAP Platform (ABAP Build Framework). 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-24872/ (Markdown: https://insights.sbomify.com/CVE-2025-24872/index.md)
```

## Sources

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

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