CVE-2025-43007
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 Service Parts Management (SPM) does not perform necessary authorization checks for an authenticated user, allowing an attacker to escalate privileges. This has low 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 Service Parts Management (SPM) contains a missing authorization check vulnerability that allows authenticated users to escalate privileges beyond their assigned role permissions. An attacker with valid credentials can perform actions reserved for higher-privileged users.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP SPM installationCheck if SAP Service Parts Management is installed in your SAP system. Query table SE11 for table SPMPACKAGE or check SAP transaction code SPAM/SAINT for installed SPM packages.Affected if SAP Service Parts Management is installed and active in the environment
-
Verify SPM versionCheck the installed SPM version by accessing SAP transaction SE03 or running report RS_MODULE_VERSION_CHECK for module SPMPARTMGMT. Compare against any vendor-released patch version information.Affected if The installed SPM version lacks the authorization patch and is earlier than the patched version
-
Check SPM authorization object configurationExecute transaction SU53 immediately after performing SPM operations to check authorization failures. Also review object S_SPM_AUTH using transaction SUIM for authorization role assignments.Affected if Users can execute SPM functions without proper S_SPM_AUTH object checks returning errors in SU53
-
Review user role assignmentsUse transaction PFCG to examine SPM-related roles assigned to users. Check for roles missing authorization objects for sensitive SPM transactions like SPMA, SPMB, or SPM1.Affected if Users possess SPM roles that lack complete authorization objects for sensitive operations, allowing actions beyond their assigned privileges
-
Audit SPM transaction usage logsReview transaction STATS or system log SM37 for SPM-specific transactions. Look for execution of high-privilege SPM functions by users lacking elevated roles.Affected if Low-privilege users have executed high-privilege SPM operations in system logs
Users are affected if SAP Service Parts Management is installed and authenticated users can perform actions beyond their assigned role permissions due to missing authorization checks.
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 in SPM using SAP's role-based access control (RBAC) framework. Review and enforce authorization objects for all sensitive operations, and assign appropriate roles to users according to the principle of least privilege.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43007 — 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-43007 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