dbcve.org
Solution Tools Plug InApplication · Sap

CVE-2026-24322

HIGH · 7.7 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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
SAP Solution Tools Plug-In (ST-PI) contains a function module that does not perform the necessary authorization checks for authenticated users, allowing sensitive information to be disclosed. This vulnerability has a high impact on confidentiality and does not affect integrity or 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

SAP Solution Tools Plug-In (ST-PI) contains a function module that fails to enforce proper authorization checks for authenticated users, allowing privilege escalation that enables unauthorized access to sensitive data. This is an access control bypass vulnerability where any authenticated user can potentially retrieve information they are not authorized to view.

MitigationApply the relevant SAP Security Note to implement proper authorization checks in the affected function module. Conduct thorough access control testing post-patch to verify users can only access data within their authorized scope.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Solution Tools Plug InApplication
Affected:= 740= 758= 2008_1_700= 2008_1_710

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 checks

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

  1. Verify ST-PI component is installed
    Log into SAP system and navigate to System > Status, or use transaction SM51 to check installed software components. Look for 'ST-PI' or 'Solution Tools Plug-In' in the component list.
    Affected if ST-PI component is not found in the installed components list, then the system is not affected by this CVE.
  2. Determine installed ST-PI version
    In SAP GUI, use transaction SAINT (SAP Add-On Installation Tool) or execute report SAPLSTPI or check the table TADIR for component ST-PI. Alternatively, use transaction SE03 and look for the ST-PI version information in the system component overview.
    Affected if The installed version matches 740, 758, 2008_1_700, or 2008_1_710 exactly.
  3. Identify the vulnerable function module
    Use transaction SE37 (Function Builder) to search for function modules within the ST-PI namespace. Look for function modules that handle sensitive data retrieval or user information access. Check transaction SUIM (User Information System) for authorization objects related to ST-PI function modules.
    Affected if A function module exists in ST-PI that can be called by any authenticated user without proper authorization checks.
  4. Verify authorization vulnerability exists
    Use transaction SU53 immediately after testing to check if a low-privileged user can access function modules they should not have access to. Alternatively, review authorization traces using transaction ST03N or auth trace via transaction SUIM > Authorization Trace.
    Affected if Authenticated users without elevated privileges can execute function modules that should require elevated or restricted authorizations.
  5. Review user access to sensitive data
    Use transaction SUIM > Users by Complex Selection Criteria or run reports to compare which users have access to sensitive tables or data via ST-PI function modules. Check transaction S_TABU_DIS for table access restrictions.
    Affected if Users with standard or limited roles can retrieve data outside their assigned authorization scope through ST-PI function modules.

The environment is affected if SAP Solution Tools Plug-In (ST-PI) version 740, 758, 2008_1_700, or 2008_1_710 is installed and any authenticated user can access function modules or data beyond their intended authorization level.

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

Apply the relevant SAP Security Note to implement proper authorization checks in the affected function module. Conduct thorough access control testing post-patch to verify users can only access data within their authorized scope.

Fix this in Solution Tools Plug In Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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