CVE-2025-42930VulnerabilityPublished 9 Sep 2025

CVE-2025-42930: SAP Business Planning and Consolidation · Unchecked Input for Loop Condition

Affects SAP Business Planning and ConsolidationSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

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: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Sep 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-26.

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 Planning and Consolidation	Affected =300 =751 =752 =753 =754 =755 =756 =757 =758 =816 =914	Fixed in–

AI-suggested

Organizations should implement the following specific mitigations: 1) Restrict and monitor user privileges to ensure only necessary users have access to SAP BPC functions, minimizing the risk of exploitation by authenticated users. 2) Implement strict input validation and parameter sanitization at the application level to detect and block abnormal loop parameters, if possible via custom SAP security configurations or application firewalls. 3) Monitor system resource usage and set alerts for unusual CPU or memory consumption patterns indicative of looping or resource exhaustion attacks. 4) Apply SAP security notes and patches promptly once available; engage with SAP support to obtain interim fixes or workarounds. 5) Conduct regular audits of SAP user activities and implement multi-factor authentication to reduce risk of credential compromise. 6) Develop and test incident response plans specifically addressing denial of service scenarios affecting SAP BPC to minimize downtime. 7) Network segmentation and limiting access to SAP BPC interfaces to trusted internal networks can reduce exposure to external attackers. These targeted measures go beyond generic advice by focusing on controlling authenticated user actions, monitoring resource usage, and preparing operational responses.

Description

SAP Business Planning and Consolidation allows an authenticated standard user to call a function module by crafting specific parameters that causes a loop, consuming excessive resources and resulting in system unavailability. This leads to high impact on the availability of the application, there is no impact on confidentiality or integrity.

Impact

For European organizations, this vulnerability poses a significant risk to business continuity and operational availability. SAP BPC is widely deployed in large enterprises for financial planning, budgeting, and consolidation, functions critical to regulatory compliance and financial reporting. An availability disruption could delay financial close processes, impair decision-making, and cause compliance issues with financial regulations such as IFRS and GDPR reporting timelines. Although confidentiality and integrity are not directly impacted, the denial of service could indirectly affect data availability for audits and regulatory submissions. The requirement for authenticated access means insider threats or compromised user credentials could be leveraged to exploit this vulnerability. Given the centrality of SAP systems in many European industries including manufacturing, finance, and public sector, the operational impact could be substantial, especially in organizations with limited redundancy or incident response capabilities.

CWE-606Unchecked Input for Loop Condition (opens in a new tab)
Base weakness
The product does not properly check inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.
Implementation
Do not use user-controlled data for loop conditions.
Implementation
Perform input validation.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (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 9 Sep 2025, 02:32 UTC

WeaknessesCWE-606

Technical details

References

Community reviews

Related threats