# CVE-2025-43002: Missing Authorization check in SAP S4/HANA (OData meta-data property)

> An authenticated attacker can access restricted information in SAP S4/HANA due to a missing authorization check in the OData meta-data property.

- **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:** 13 May 2025
- **Updated:** 13 May 2025
- **Also known as:** GHSA-v2rg-3wmw-65x9

## What is CVE-2025-43002?

CVE-2025-43002 is a medium-severity missing authorization vulnerability in SAP_SE SAP S4/HANA (OData meta-data property), published on 13 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP S4CORE OData meta-data property allows an authenticated attacker to access restricted information due to missing authorization check. This could cause a low impact on confidentiality but integrity and availability of the application are not impacted.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

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


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

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

## Is CVE-2025-43002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-43002 is a medium-severity missing authorization vulnerability in SAP_SE SAP S4/HANA (OData meta-data property), published on 13 May 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-43002 in the wild and no public exploit code.

Affected product: SAP_SE SAP S4/HANA (OData meta-data property). 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-43002/ (Markdown: https://insights.sbomify.com/CVE-2025-43002/index.md)
```

## Sources

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

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