dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-40132

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-12
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
Due to missing authorization check in SAP Strategic Enterprise Management (Scorecard Wizard in Business Server Pages), an authenticated attacker could access information that they are otherwise unauthorized to view. This vulnerability also enables the attacker to change the default settings and modify value fields, which will mislead risk evaluations and falsely lower assessed risk levels. This results in a low impact on the confidentiality and integrity of the data. There is no impact on the application�s availability.

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

This is a missing authorization check vulnerability in SAP Strategic Enterprise Management's Scorecard Wizard component within Business Server Pages (BSP). An authenticated attacker can bypass authorization to access unauthorized information and modify default settings/value fields, which can mislead risk evaluations by falsely lowering assessed risk levels. This is effectively an Insecure Direct Object Reference (IDOR) or broken access control issue.

MitigationImplement proper authorization checks in the Scorecard Wizard to verify user permissions before allowing access to information or modification of settings and value fields.

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP Strategic Enterprise Management installation
    Check your SAP system for the presence of the Strategic Enterprise Management (SEM) module. Use SAP transaction code SE16 or SPAM to list installed software components and look for component names containing 'SEM' or 'Strategic Enterprise Management'.
    Affected if The SEM module is installed and the Scorecard Wizard component is present in the BSP application.
  2. Locate the Scorecard Wizard BSP application
    In the SAP system, use transaction code SE80 or SE71 to search for BSP applications containing 'Scorecard' or 'Wizard' in the name. Check the repository browser for Business Server Pages applications under the SEM namespace.
    Affected if A BSP application named Scorecard Wizard or similar is found in the system.
  3. Verify Scorecard Wizard authorization roles
    Use transaction code PFCG to examine roles assigned to users who access the Scorecard Wizard. Check if roles contain authorization objects specifically for the Scorecard Wizard BSP application (look for S_DEVELOP with OBJTYPE=BSP or S_BSP_DS).
    Affected if Roles exist that grant access to the Scorecard Wizard without object-specific authorization checks for the affected BSP component.
  4. Test unauthorized access to Scorecard Wizard functions
    As a low-privilege user without administrative access to the Scorecard Wizard, attempt to access the BSP application directly via URL or transaction code and try to modify settings, default values, or view restricted scorecard data.
    Affected if A user without explicit Scorecard Wizard permissions can access the application or modify settings/value fields.
  5. Review BSP application authorization configuration
    Use transaction code SE80 to open the Scorecard Wizard BSP application and check the OnRequest or OnInitialization event handlers for authorization checks. Look for function modules like AUTHORITY_CHECK or checks against authorization objects before executing operations.
    Affected if The BSP application code lacks proper AUTHORITY_CHECK calls or permission validation before allowing access to modify settings or view data.

A user is affected if the SAP Strategic Enterprise Management Scorecard Wizard BSP application is installed and lacks proper authorization checks in its code, allowing unauthorized access or modification of scorecard settings.

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

Implement proper authorization checks in the Scorecard Wizard to verify user permissions before allowing access to information or modification of settings and value fields.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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