CVE-2026-24313
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 Solution Tools Plug-In (ST-PI) contains a function module that does not perform the necessary authorization checks for authenticated users, allowing system information to be disclosed. This vulnerability has a low 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 confidenceSAP Solution Tools Plug-In (ST-PI) contains a function module that fails to perform necessary authorization checks for authenticated users, allowing unauthorized access to system information. This is a broken access control vulnerability where the module trusts authenticated users without validating their authorization to access specific data.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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 ST-PI installation and versionLog into SAP system and navigate to System -> Status or use transaction SM51 to check installed software components. Look for ST-PI in the component list and record the version number.Affected if ST-PI is installed and the version matches or falls within the affected version range (compare your installed version to known affected ranges for this CVE).
-
Identify the affected function moduleUse SAP transaction SE37 (Function Builder) or SE80 to search for function modules within ST-PI that handle system information retrieval. Consult SAP security notes for this CVE to identify the specific function module name.Affected if The vulnerable function module exists in your ST-PI installation and is accessible without proper authorization checks.
-
Review user access to the function moduleUse transaction SUIM (User Information System) or directly test access to the identified function module with different user accounts. Check which authenticated users can execute the module.Affected if Users who should not have access to system information are able to execute the function module.
-
Verify authorization configuration for the moduleUse transaction SU53 immediately after a user attempts to access the function module to check which authorization objects failed. Use transaction SUI3 to review authorization profiles assigned to users accessing ST-PI functions.Affected if The function module is executing without checking SAP authorization objects, or users lack proper authorization objects but can still access the module.
Your environment is affected if SAP ST-PI is installed with a vulnerable version and the function module can be accessed by users who should not have authorization to retrieve system information.
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 affected function module using appropriate SAP authorization objects to verify user permissions before disclosing system information. Apply any available SAP security notes for ST-PI addressing this authorization bypass.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24313 — 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-2026-24313 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