CVE-2025-42960VulnerabilityPublished 8 Jul 2025

CVE-2025-42960: SAP Business Warehouse and SAP BW/4HANA BEx Tools · Missing Authorization

Affects SAP Business Warehouse and SAP BW/4HANA BEx ToolsSource 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 13% 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:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 8 Jul 2025
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_SE SAP Business Warehouse and SAP BW/4HANA BEx Tools	Affected =200 =300 =400 =701 =702 =731 =740 =750 =751 =752 =753 =754 =755 =756 =757 =758 =816	Fixed in–

AI-suggested

To mitigate CVE-2025-42960, European organizations should implement the following specific measures: 1) Conduct a thorough audit of user privileges within SAP BW and SAP BW/4HANA environments to ensure the principle of least privilege is enforced, minimizing the number of users with elevated access rights. 2) Implement strict access controls and monitoring on user table modification operations, including logging and alerting on deletion or modification activities. 3) Review and harden authorization objects and roles related to BEx Tools and SAP BW components to detect and close gaps in authorization checks. 4) Employ multi-factor authentication (MFA) for all SAP BW users to reduce the risk of credential compromise. 5) Monitor SAP security notes and vendor advisories closely for the release of official patches or hotfixes addressing this vulnerability and apply them promptly once available. 6) Use SAP’s Security Audit Log and change management tools to detect anomalous activities indicative of exploitation attempts. 7) Train SAP administrators and security teams on recognizing and responding to potential misuse of authorization privileges. These targeted actions go beyond generic patching advice by focusing on privilege management, monitoring, and proactive detection tailored to the SAP BW environment.

Description

SAP Business Warehouse and SAP BW/4HANA BEx Tools allow an authenticated attacker to gain higher access levels than intended by exploiting improper authorization checks. This could potentially impact data integrity by allowing deletion of user table entries.�It has no impact on the confidentiality and availability of the application.

Impact

For European organizations, the impact of CVE-2025-42960 centers on the potential compromise of data integrity within critical SAP Business Warehouse systems. SAP BW is widely used across Europe in sectors such as manufacturing, finance, retail, and public administration for business intelligence and data analytics. Unauthorized deletion of user table entries could lead to inaccurate reporting, loss of audit trails, and disruption of business processes dependent on reliable data. While confidentiality and availability are not directly affected, the integrity compromise could result in incorrect business decisions, regulatory compliance issues, and potential financial losses. Organizations relying heavily on SAP BW for operational reporting and decision-making may experience degraded trust in their data outputs. Additionally, since exploitation requires authenticated access with some privileges, insider threats or compromised credentials could be leveraged to exploit this vulnerability. The absence of known exploits reduces immediate risk, but the broad range of affected versions and the critical role of SAP BW in European enterprises necessitate prompt attention.

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 8 Jul 2025, 00:58 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats