# CVE-2025-42891: Missing Authorization check in SAP Enterprise Search for ABAP

> An attacker with high privileges can read and export database table contents due to a missing authorization check in SAP Enterprise Search for ABAP.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-49g3-m6hr-79hv

## What is CVE-2025-42891?

CVE-2025-42891 is a medium-severity missing authorization vulnerability in SAP_SE SAP Enterprise Search for ABAP, published on 9 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Due to a missing authorization check in SAP Enterprise Search for ABAP, an attacker with high privileges may read and export the contents of database tables into an ABAP report. This could lead to a high impact on data confidentiality and a low impact on data integrity. There is no impact on application's availability.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-42891 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42891 is a medium-severity missing authorization vulnerability in SAP_SE SAP Enterprise Search for ABAP, published on 9 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42891 in the wild and no public exploit code.

Affected product: SAP_SE SAP Enterprise Search for ABAP. 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-42891/ (Markdown: https://insights.sbomify.com/CVE-2025-42891/index.md)
```

## Sources

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

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