dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-42912

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SAP HCM My Timesheet 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SAP HCM My Timesheet Fiori 2.0 application lacks proper authorization validation for authenticated users, allowing authenticated users to perform actions or access data outside their assigned privilege scope, leading to privilege escalation with significant integrity impact.

MitigationImplement and enforce role-based authorization checks within the Fiori application and underlying SAP backend using SAP's GRC framework and PFCG role configuration to validate user permissions before executing privileged operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP HCM My Timesheet Fiori 2.0 deployment
    Access SAP Fiori Launchpad and locate the 'My Timesheet' application under HCM module, or query SAP backend system for Fiori app package identification using transaction /IWFND/MAINT_SERVICE to list active OData services
    Affected if The My Timesheet Fiori 2.0 application is present and active in the Fiori launchpad
  2. Verify user role assignments for timesheet functionality
    Use SAP transaction PFCG (Role Maintenance) or SUIM (User Information System) to examine roles assigned to users who have access to My Timesheet, checking for excessive or mismatched role assignments
    Affected if Users possess roles that grant privileged actions beyond their intended timesheet submission scope
  3. Inspect authorization objects in timesheet-related roles
    Execute transaction SU24 within SAP to review authorization objects assigned to roles used for My Timesheet, focusing on HCM-related authorization objects like P_TDIS, P_TCLA, or custom authorization objects
    Affected if Roles lack proper authorization object restrictions or contain wildcard entries allowing escalated privileges
  4. Check for missing GRC role validation
    Review SAP GRC (Governance Risk and Compliance) configuration by accessing transaction GRAC_RULE or GRAC_REQUEST to determine if authorization checks are enforced through GRC workflows for timesheet operations
    Affected if GRC authorization validation is not configured or is bypassed for the My Timesheet application
  5. Audit recent timesheet submissions for privilege escalation indicators
    Use transaction CAT2 or HRRCF_TS_AUTHORITY_CHECK (if available) to query timesheet submission logs and identify submissions made by standard users that modified data outside their organizational assignment
    Affected if Standard users have submitted or modified timesheet entries for other employees or cost centers

A user is affected if the My Timesheet Fiori 2.0 application is deployed and users have roles or authorization objects that allow actions beyond their assigned organizational scope, enabling unauthorized access to other employees' timesheet data or functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement and enforce role-based authorization checks within the Fiori application and underlying SAP backend using SAP's GRC framework and PFCG role configuration to validate user permissions before executing privileged operations.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-42912 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-42912 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data