# CVE-2025-42913: Missing Authorization check in SAP HCM (My Timesheet Fiori 2.0 application)


- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-pm6j-4v44-3wr7

## What is CVE-2025-42913?

CVE-2025-42913 is a low-severity vulnerability in SAP_SE SAP HCM (My Timesheet Fiori 2.0 application), published on 9 Sep 2025. 

### Official description

Due to missing authorization checks, SAP HCM My Timesheet Fiori 2.0 application allows an authenticated attacker with in-depth system knowledge to escalate privileges and perform activities that are otherwise restricted, resulting in a low impact on the integrity of the application. Confidentiality and availability are not impacted.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-42913 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42913 is a low-severity vulnerability in SAP_SE SAP HCM (My Timesheet Fiori 2.0 application), published on 9 Sep 2025. 
Exploitation: There is no known exploitation of CVE-2025-42913 in the wild and no public exploit code.

Affected product: SAP_SE SAP HCM (My Timesheet Fiori 2.0 application). 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-42913/ (Markdown: https://insights.sbomify.com/CVE-2025-42913/index.md)
```

## Sources

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

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