CVE-2025-42917 Missing Authorization check in SAP HCM (Approve Timesheets Fiori 2.0 application)
Medium 6.5
Published
Updated
Check this codebase for CVE-2025-42917 and fix it if it is affected.
What it is: CVE-2025-42917 is a medium-severity vulnerability in SAP_SE SAP HCM (Approve Timesheets Fiori 2.0 application), published on 9 Sep 2025.
Exploitation: There is no known exploitation of CVE-2025-42917 in the wild and no public exploit code.
Affected product: SAP_SE SAP HCM (Approve Timesheets 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-42917/ (Markdown: https://insights.sbomify.com/CVE-2025-42917/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-42917?
CVE-2025-42917 is a medium-severity vulnerability in SAP_SE SAP HCM (Approve Timesheets Fiori 2.0 application), published on 9 Sep 2025.
Official description
SAP HCM Approve Timesheets Fiori 2.0 application does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges. This issue has a significant impact on the application's integrity, while confidentiality and availability remain unaffected.
Weakness: CWE-862
Which versions are affected by CVE-2025-42917?
How do I fix CVE-2025-42917?
No fix has been published for CVE-2025-42917 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-42917 being exploited?
There is no known exploitation of CVE-2025-42917 in the wild and no public exploit code.
Sources
Also known as GHSA-xxh2-9vx8-x442.