CVE-2026-24327VulnerabilityPublished 10 Feb 2026

CVE-2026-24327: SAP Strategic Enterprise Management (Balanced Scorecard in BSP Application) · Missing Authorization

Affects SAP Strategic Enterprise Management (Balanced Scorecard in BSP Application)Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% 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 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 Strategic Enterprise Management (Balanced Scorecard in BSP Application)	Affected =602 =603 =604 =605 =634 =700 =736 =746 =747 =748 =800	Fixed in–

AI-suggested

1. Apply SAP security patches promptly once released for the affected SEM-BW versions to remediate the missing authorization checks. 2. Conduct a thorough review and audit of SAP user roles and authorizations, focusing on the Balanced Scorecard BSP application, to ensure least privilege principles are enforced. 3. Implement strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise. 4. Enable detailed logging and monitoring of SAP SEM access, with alerts for anomalous access patterns or privilege escalations. 5. Restrict network access to SAP SEM applications using segmentation and firewall rules to limit exposure to trusted users only. 6. Educate SAP administrators and users about the risks of insider threats and the importance of safeguarding credentials. 7. Consider deploying SAP Enterprise Threat Detection tools or third-party solutions to identify suspicious activities related to authorization bypass attempts. 8. Regularly review and update SAP security policies and conduct penetration testing focused on authorization controls within SAP SEM.

Description

CVE-2026-24327 is a medium-severity vulnerability in SAP Strategic Enterprise Management's Balanced Scorecard BSP application caused by a missing authorization check. An authenticated attacker with legitimate access could view information they are not authorized to see, impacting confidentiality with no effect on integrity or availability. The vulnerability affects multiple versions of the SEM-BW product line. Exploitation requires network access and low complexity but does not require user interaction. No known exploits are currently in the wild. European organizations using affected SAP SEM versions may face risks of unauthorized data disclosure. Mitigation involves applying SAP patches when available, reviewing and tightening authorization roles, and monitoring access logs for suspicious activity. Countries with significant SAP enterprise deployments and critical industries relying on SAP SEM, such as Germany, France, and the UK, are most likely affected.

Impact

For European organizations, this vulnerability poses a risk of unauthorized information disclosure within SAP SEM environments, which are widely used for strategic planning and performance management in large enterprises. The confidentiality breach could expose sensitive corporate data such as key performance indicators, strategic goals, and business metrics. While the impact on operational integrity and availability is nil, the leakage of confidential data could lead to competitive disadvantage, regulatory compliance issues (especially under GDPR if personal data is involved), and reputational damage. Industries such as manufacturing, finance, and utilities that rely heavily on SAP SEM for decision-making are particularly at risk. Since exploitation requires authenticated access, the threat is more pronounced from insider threats or attackers who have compromised legitimate credentials. The absence of known exploits reduces immediate risk but does not eliminate the potential for targeted attacks. Organizations with complex SAP role management may find it challenging to detect unauthorized access without enhanced monitoring.

Summary

CVE-2026-24327 is a vulnerability classified under CWE-862 (Missing Authorization) found in SAP Strategic Enterprise Management (SEM), specifically within the Balanced Scorecard component implemented as a Business Server Pages (BSP) application. The flaw arises because the application fails to enforce proper authorization checks on certain functions or data views, allowing an authenticated user to access information beyond their assigned permissions. This vulnerability affects a broad range of SEM-BW versions, from 600 through 800, indicating a long-standing issue across multiple product releases. The CVSS v3.1 base score is 4.3 (medium), reflecting that the attack vector is network-based (AV:N), with low attack complexity (AC:L), requiring privileges (PR:L) but no user interaction (UI:N). The impact is limited to confidentiality (C:L), with no impact on integrity or availability. Since the attacker must already be authenticated, the risk is constrained to insider threats or compromised accounts. No public exploits have been reported, and SAP has not yet published patches at the time of this report. The vulnerability could allow unauthorized disclosure of sensitive business data managed within the Balanced Scorecard application, potentially exposing strategic or performance metrics that could be leveraged for competitive or malicious purposes.

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

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats