# CVE-2025-43008: Missing Authorization check in SAP S/4HANA HCM Portugal and SAP ERP HCM Portugal

> An unauthorized user can view files of other companies, leading to disclosure of personal employee data in SAP HCM Portugal.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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:** 13 May 2025
- **Updated:** 13 May 2025
- **Also known as:** GHSA-xvx6-286h-35qm

## What is CVE-2025-43008?

CVE-2025-43008 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA HCM Portugal and SAP ERP HCM Portugal, published on 13 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Due to missing authorization check, an unauthorized user can view the files of other company. This might lead to disclosure of personal data of employees. There is no impact on integrity and availability.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-43008 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-43008 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA HCM Portugal and SAP ERP HCM Portugal, published on 13 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-43008 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA HCM Portugal and SAP ERP HCM Portugal. 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-43008/ (Markdown: https://insights.sbomify.com/CVE-2025-43008/index.md)
```

## Sources

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

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