VulnerabilityPublished 10 Feb 2026

CVE-2026-23681: SAP Support Tools Plug-In · Missing Authorization

Affects SAP Support Tools Plug-InSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% 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:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 Support Tools Plug-In	Affected =2008_1_710 =740 =758	Fixed in–

AI-suggested

Restrict access to SAP Support Tools Plug-In function modules by enforcing strict role-based access controls (RBAC) and least privilege principles.
Monitor and audit SAP user activities, especially those involving support tool modules, to detect anomalous access patterns.
Implement network segmentation and firewall rules to limit access to SAP management interfaces only to trusted administrators.
Apply SAP security notes and patches promptly once available for the affected ST-PI versions.
Use SAP’s security configuration guides to harden system settings and disable unnecessary function modules or services.
Conduct regular SAP system security assessments and penetration tests focusing on authorization checks.
Educate SAP administrators about the risks of information disclosure and the importance of credential protection.
Consider deploying SAP Enterprise Threat Detection tools to identify suspicious activities related to this vulnerability.
If patching is delayed, implement compensating controls such as enhanced logging and alerting on access to vulnerable modules.

Description

CVE-2026-23681 is a medium-severity vulnerability in the SAP Support Tools Plug-In caused by missing authorization checks in certain function modules. An authenticated attacker with low privileges can exploit this flaw to retrieve sensitive system and configuration information. While the vulnerability does not impact system integrity or availability, the disclosure of system details could aid attackers in planning further attacks. The affected SAP Support Tools Plug-In versions include ST-PI 2008_1_700, 2008_1_710, 740, and 758. Exploitation requires authentication but no user interaction. No known public exploits exist yet. European organizations using these SAP versions should prioritize patching or mitigating this issue to prevent information leakage that could facilitate more severe attacks.

Impact

For European organizations, this vulnerability poses a moderate risk primarily through information disclosure. SAP systems are widely used across Europe in sectors such as manufacturing, finance, public administration, and utilities. Attackers gaining system configuration details can tailor attacks such as privilege escalation, targeted phishing, or exploitation of other SAP vulnerabilities. Although the direct impact on confidentiality is low, the indirect risk of enabling more severe attacks is significant, especially in critical infrastructure and large enterprises with complex SAP landscapes. The lack of impact on integrity and availability reduces immediate operational risk but does not eliminate the threat of subsequent compromise. Organizations with exposed or poorly segmented SAP environments are at higher risk. Given the strategic importance of SAP systems in European economies, attackers may prioritize these targets to gain footholds or conduct espionage. The requirement for authenticated access limits exposure but insider threats or compromised credentials could facilitate exploitation.

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:35 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats