dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-42984

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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 S/4HANA Manage Central Purchase Contract does not perform necessary authorization checks for an authenticated user. Due to this, an attacker could execute the function import on the entity making it inaccessible for unrestricted user. This has low impact on confidentiality and availability of the application.

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 · moderate confidence

SAP S/4HANA Manage Central Purchase Contract lacks proper authorization checks for authenticated users, allowing a user to execute function imports on entities that should be restricted. This makes those entities inaccessible to unrestricted users, exploiting the authorization logic flaw.

MitigationApply the relevant SAP security note/patch for this authorization vulnerability and review role-based access controls (RBAC) in the affected S/4HANA system to ensure proper separation of duties.

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
Low
Integrity
None
Availability
Low

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

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 if the system is SAP S/4HANA
    Execute transaction SM51 or use SAP MII to display the system name and release. Alternatively, check transaction SXMB_MONI for integration engine version or use SAP administrative reports to confirm the S/4HANA installation.
    Affected if The system is running SAP S/4HANA (on-premise or private cloud edition) in any version.
  2. Verify access to Manage Central Purchase Contract
    Check if the SAP Fiori app 'Manage Central Purchase Contract' (F4711) or the corresponding SAP GUI transaction (typically ME31K or custom transaction) is available in the system by reviewing the Fiori app catalog or transaction menu.
    Affected if The Fiori app or transaction for Manage Central Purchase Contract is deployed and accessible to users.
  3. Review user role assignments for Purchase Contract functions
    Use transaction SUIM (User Information System) to search for users assigned to roles containing authorization objects for Purchasing contracts (e.g., M_EINK_AB, M_EINK_FG). Cross-check with transaction PFCG for role definitions.
    Affected if Users without elevated purchasing privileges have roles that include function import execution rights on purchase contract entities.
  4. Check authorization objects for restricted entities
    Execute transaction SU53 immediately after a user attempts to access restricted purchase contract entities. Also review authorization traces via transaction ST01 or auth trace in transaction SAAB to identify authorization object failures related to function imports on purchase contracts.
    Affected if Authenticated users can execute function imports on purchase contract entities that should be restricted by authorization checks, evidenced by successful access despite lacking proper authorization objects.
  5. Inspect PFCG role configuration for Purchase Contract authorizations
    Open transaction PFCG and examine roles assigned to users who access Manage Central Purchase Contract. Verify that authorization objects (especially M_EINK_AB for purchasing contracts and any custom auth objects for function imports) are properly restricted to specific purchasing organizations or contract types.
    Affected if Roles allow unrestricted function import execution on purchase contracts without proper field-level restrictions (e.g., purchasing organization, contract type).

A user is affected if the system is SAP S/4HANA with the Manage Central Purchase Contract functionality enabled and authenticated users can access or modify restricted purchase contract entities through function imports without proper authorization failures being raised.

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

Apply the relevant SAP security note/patch for this authorization vulnerability and review role-based access controls (RBAC) in the affected S/4HANA system to ensure proper separation of duties.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-42984 — 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-42984 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