VulnerabilityPublished 10 Mar 2026

CVE-2026-24313: SAP Solution Tools Plug-In (ST-PI) · Missing Authorization

Affects SAP Solution Tools Plug-In (ST-PI)Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.0 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SAP_SESAP Solution Tools Plug-In (ST-PI)	Affected =2008_1_710 =740 =758	Fixed in–

AI-suggested

To mitigate CVE-2026-24313 effectively, organizations should: 1) Conduct a thorough audit of authorization checks within the SAP ST-PI environment, focusing on the vulnerable function modules to ensure proper access controls are enforced. 2) Restrict access to the SAP Solution Tools Plug-In to only trusted and necessary users, applying the principle of least privilege rigorously. 3) Monitor SAP system logs for unusual access patterns or attempts to invoke the vulnerable functions by unauthorized users. 4) Implement network segmentation and access controls to limit exposure of SAP management interfaces to trusted networks and personnel only. 5) Stay informed about SAP security advisories and apply patches or updates promptly once available. 6) Consider deploying SAP's security notes or temporary compensating controls, such as disabling or restricting the vulnerable module if feasible. 7) Enhance internal user authentication mechanisms, including multi-factor authentication, to reduce the risk of compromised credentials being used to exploit this vulnerability. 8) Train SAP administrators and security teams on the importance of authorization checks and secure configuration management within SAP environments. These targeted actions go beyond generic advice by focusing on authorization validation, access restriction, and proactive monitoring specific to the SAP ST-PI context.

Description

SAP 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.

Impact

The primary impact of CVE-2026-24313 is the unauthorized disclosure of system information within SAP environments using the affected ST-PI versions. While the confidentiality impact is low, the exposure of system details can aid attackers in reconnaissance activities, potentially facilitating more targeted attacks or privilege escalation attempts. Since integrity and availability are not affected, the immediate operational disruption risk is minimal. However, the information leakage can weaken the overall security posture of an organization by revealing configuration details, system versions, or other sensitive metadata. Organizations relying heavily on SAP for critical business processes may face increased risk if attackers leverage this information to craft further exploits. The vulnerability requires authenticated access with some privileges, so insider threats or compromised accounts pose a significant risk vector. The absence of known exploits reduces immediate threat but does not eliminate the risk, especially as attackers often develop exploits post-disclosure. The medium severity rating suggests organizations should address this vulnerability promptly to prevent potential escalation and information leakage.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 01:05 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats