CVE-2026-24322VulnerabilityPublished 10 Feb 2026

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

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

Not known to be exploited · CVSS 7.7 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.7High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% 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:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

1. Monitor SAP security advisories closely and apply official patches or updates from SAP as soon as they become available for the affected ST-PI versions. 2. Until patches are released, implement strict role-based access controls (RBAC) to limit the number of users with any privileges on the ST-PI plug-in. 3. Conduct thorough audits of user privileges and remove unnecessary access rights, especially for function modules related to ST-PI. 4. Enable detailed logging and monitoring of SAP function module calls to detect anomalous or unauthorized access attempts. 5. Use SAP’s security tools to enforce authorization checks and validate that no unauthorized function calls are possible. 6. Educate SAP administrators and security teams about this vulnerability to ensure rapid detection and response. 7. Consider network segmentation and isolation of SAP management interfaces to reduce exposure. 8. Employ multi-factor authentication (MFA) for SAP system access to reduce risk from compromised credentials. 9. Regularly review and update SAP security configurations and hardening guides to minimize attack surface. 10. Engage with SAP support and security communities to stay informed about emerging threats and mitigation best practices.

Description

CVE-2026-24322 is a high-severity vulnerability in the SAP Solution Tools Plug-In (ST-PI) that results from missing authorization checks in a function module. Authenticated users with low privileges can exploit this flaw to access sensitive information without proper permissions. The vulnerability impacts confidentiality but does not affect data integrity or system availability. It affects multiple versions of ST-PI, including 2008_1_700, 2008_1_710, 740, and 758. The CVSS score of 7.7 reflects the ease of exploitation over the network with low privileges and no user interaction required. No known exploits are currently reported in the wild. European organizations using affected SAP versions are at risk of sensitive data disclosure, which could lead to compliance violations and reputational damage. Mitigation requires applying vendor patches once available or implementing strict access controls and monitoring for unusual access patterns. Countries with significant SAP deployments and critical industries relying on SAP ERP systems are more likely to be targeted.

Impact

For European organizations, the primary impact is the unauthorized disclosure of sensitive information managed within SAP environments. This could include financial data, customer records, intellectual property, or strategic business information. Such data breaches can lead to regulatory penalties under GDPR, loss of customer trust, and competitive disadvantage. Since the vulnerability does not affect integrity or availability, operational disruption is unlikely, but confidentiality breaches alone can have severe legal and financial repercussions. Industries such as manufacturing, finance, healthcare, and public sector entities in Europe that heavily depend on SAP solutions are particularly at risk. The ability for low-privilege authenticated users to access sensitive data increases the insider threat risk and the potential impact of compromised credentials. Additionally, the cross-scope nature of the vulnerability means that attackers could access data beyond their immediate privileges, amplifying the damage. The absence of known exploits in the wild provides a window for proactive mitigation, but the high CVSS score underscores the urgency of addressing this vulnerability.

Summary

CVE-2026-24322 is a vulnerability classified under CWE-862 (Missing Authorization) found in the SAP Solution Tools Plug-In (ST-PI). The issue arises because a specific function module within ST-PI does not enforce necessary authorization checks for authenticated users. This means that users with legitimate but limited access can invoke this function module to retrieve sensitive information that should otherwise be restricted. The vulnerability affects several versions of ST-PI, notably 2008_1_700, 2008_1_710, 740, and 758. The CVSS 3.1 base score is 7.7, indicating a high severity level. The vector indicates the attack can be performed remotely (AV:N) with low attack complexity (AC:L), requiring privileges (PR:L) but no user interaction (UI:N). The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially compromised component. The impact is high on confidentiality (C:H) but none on integrity (I:N) or availability (A:N). This vulnerability could allow unauthorized disclosure of sensitive business data, potentially exposing intellectual property, financial information, or personal data. Although no exploits are currently known in the wild, the vulnerability's characteristics make it a significant risk for organizations relying on affected SAP components. The lack of authorization checks is a fundamental security flaw that could be leveraged by insiders or attackers who have gained limited access to SAP systems. Given SAP's widespread use in enterprise resource planning and critical business functions, exploitation could have serious consequences.

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 17 Feb 2026, 09:38 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats