CVE-2025-43011
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, SAP Landscape Transformation's PCL Basis module does not perform the necessary authorization checks, allowing authenticated users to access restricted functionalities or data. This can lead to a high impact on confidentiality with no impact on the integrity or 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 Landscape Transformation's PCL Basis module lacks proper authorization checks under certain conditions, allowing authenticated users to bypass access controls and view restricted data or functionalities. This is a classic Insecure Direct Object Reference (IDOR) or broken access control vulnerability where the application fails to validate user permissions before granting access to sensitive information.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP Landscape Transformation installationLocate the SAP LT system in your environment and identify the installed component version. On SAP systems, use transaction code SM37 to check running jobs, or transaction SE16N to query table SAPCMPROC for component information. Alternatively, check transaction SAINT for installed software components.Affected if SAP Landscape Transformation is installed and the version has not been patched to include the security note for this CVE.
-
Identify PCL Basis module presenceUsing SAP transaction code SE11 or SE16, query table TADIR for objects related to 'PCL' or 'PCL Basis'. Alternatively, use transaction SPAM to check for patches containing PCL-related components.Affected if The PCL Basis module is present in the SAP LT installation.
-
Verify authorization object configuration for PCLExecute transaction code SUIM to search for authorization objects related to PCL. Check objects like S_TCODE, S_PROGRAM, or custom PCL-specific authorization objects. Review field values to ensure they restrict access appropriately.Affected if Authorization objects for PCL are missing, set to broad values (like '*'), or allow unrestricted access to authenticated users.
-
Review user role assignments for PCL accessUse transaction code PFCG to examine roles assigned to users who access PCL Basis. Check role menus and authorization data to determine if roles grant excessive or unchecked access to PCL functionalities.Affected if Users possess roles that grant PCL access without proper authorization checks enforced through role restrictions.
A system is affected if it runs SAP Landscape Transformation with the PCL Basis module and the authorization controls for PCL have not been hardened to enforce proper permission checks, allowing authenticated users unintended access to restricted data or functions.
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 dataApply the relevant SAP Security Note to implement proper authorization checks in the PCL Basis module. Additionally, review and restrict user roles and permissions to align with the principle of least privilege until the patch is applied.
- Consultation8.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43011 — 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-43011 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