CVE-2025-43000
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 · uneditedUnder certain conditions Promotion Management Wizard (PMW) allows an attacker to access information which would otherwise be restricted.This has High impact on Confidentiality with Low impact on 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 confidenceCVE-2025-43000 is an access control vulnerability in SAP's Promotion Management Wizard (PMW) module. Under certain conditions, an attacker can access information that would otherwise be restricted, indicating a broken access control or insecure direct object reference (IDOR) vulnerability. The high confidentiality impact suggests sensitive data exposure, while low integrity and availability impact indicates the flaw is primarily about unauthorized data viewing rather than modification or disruption.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/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 PMW module installationCheck your SAP system for the Promotion Management Wizard component by querying transaction SE11 for table DMF_TC_COMP where COMPONENT contains 'PROMOTION' or check via transaction SA01 for PMW-related packages.Affected if PMW module is installed in your SAP environment
-
Identify PMW versionAccess transaction SPAM or SUMA and check installed support packages for Promotion Management component, or query table VERFIELDS for PMW-related entries to determine the specific PMW version deployed.Affected if Installed PMW version falls within any affected range that may exist for this CVE
-
Verify PMW web interface exposureCheck transaction SICF for active PMW-related services under /sap/bc/rest/ or similar PMW endpoints, and review web dispatcher configuration for PMW access paths.Affected if PMW web services are active and exposed (even internally)
-
Review PMW access control configurationsExecute transaction SU53 immediately after attempting PMW data access to check authorization failures, and review role definitions via transaction PFCG for objects S_DM_PROMOTION or similar PMW-specific auth objects.Affected if Users without proper PMW roles can access PMW data or functions
-
Audit PMW data access logsCheck transaction ST03N and audit logs for PMW-specific transactions (such as PMW transaction codes if known) to identify any access patterns to restricted promotion data by unauthorized users.Affected if Logs show PMW data access by users lacking explicit promotion management permissions
A user is affected if they run the SAP Promotion Management Wizard module and the system allows unauthorized users to view restricted promotion data due to missing or broken access control 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 the Promotion Management Wizard to verify user permissions before allowing access to any data or functionality. Conduct access control testing across all PMW functions to identify and remediate similar authorization gaps.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43000 — 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-43000 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