CVE-2025-42982
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 · uneditedSAP GRC allows a non-administrative user to access and initiate transaction which could allow them to modify or control the transmitted system credentials. This causes high impact on confidentiality, integrity 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 confidenceSAP GRC contains a broken access control vulnerability where a non-administrative user can access and execute a specific transaction that should be restricted to administrators. This unauthorized transaction access allows the attacker to modify or control system credentials transmitted by the application, compromising the confidentiality, integrity, and availability of the SAP GRC system.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP GRC installation and versionExecute transaction code SM37 or use transaction SAINT (SAP Installation Assistant) to list installed SAP GRC components and their version numbers. Alternatively, query table VERSION for GRC-related components.Affected if SAP GRC is installed and the version matches the affected range (if known) or if the version cannot be determined and the vulnerability applies.
-
Identify the affected restricted transactionReview SAP GRC configuration documentation or audit logs (transaction code SLG1) to identify which transaction is supposed to be restricted to administrators for credential management functions.Affected if Non-administrative users have access to execute the transaction that should be restricted to administrators.
-
Audit user role assignments for the restricted transactionExecute transaction code SUIM (User Information System), then use 'Roles by Complex Selection' to list all users assigned roles that contain the affected transaction. Cross-reference with the list of users who should NOT have administrative access.Affected if Non-administrative users are assigned roles that allow execution of the restricted transaction.
-
Review SAP_GRFCAuthority role assignmentsExecute transaction code PFCG to view the SAP_GRFCAuthority role definition and its assigned transaction codes. Check user assignments to this role using transaction code SU01 or SUIM.Affected if The SAP_GRFCAuthority role is assigned to non-administrative users, or the role permits access to the restricted transaction.
-
Check for unauthorized credential access attemptsReview SAP GRC audit logs (transaction code SLG1) and system logs (transaction code SM37) for any execution of the restricted transaction by non-administrative users.Affected if Audit logs show execution of the restricted transaction by users without administrative privileges.
A user is affected if non-administrative users have been granted access to execute the restricted credential management transaction, as evidenced by role assignments or audit logs.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks on the affected transaction and enforce role-based access controls (RBAC) to ensure only authorized administrators can access credential management functions. Review and restrict the SAP_GRFCAuthority role assignments.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-42982 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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