# CVE-2025-42949: Missing Authorization check in ABAP Platform

> An authenticated user can bypass authorization checks via the SQL Console to read database table contents, compromising data confidentiality.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/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:** 12 Aug 2025
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-v5mq-3g8r-vp97

## What is CVE-2025-42949?

CVE-2025-42949 is a medium-severity missing authorization vulnerability in SAP_SE ABAP Platform, published on 12 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Due to a missing authorization check in the ABAP Platform, an authenticated user with elevated privileges could bypass authorization restrictions for common transactions by leveraging the SQL Console. This could enable an attacker to access and read the contents of database tables without proper authorization, leading to a significant compromise of data confidentiality. However, the integrity and availability of the system remain unaffected.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-42949 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42949 is a medium-severity missing authorization vulnerability in SAP_SE ABAP Platform, published on 12 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42949 in the wild and no public exploit code.

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

## Sources

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

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