CVE-2025-42988VulnerabilityPublished 10 Jun 2025

CVE-2025-42988: SAP Business Objects Business Intelligence Platform · Server-Side Request Forgery

Affects SAP Business Objects Business Intelligence PlatformSource CVE Database V5

Not known to be exploited · CVSS 3.7 Low.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

3.7Low

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:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 Jun 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 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 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_se/sap-business-objects-business-intelligence-platform`pkg:rpm/sap_se/sap-business-objects-business-intelligence-platform`Other threats	Affected =2025 =2027	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Network Segmentation: Implement strict network segmentation and firewall rules to limit the SAP Business Objects platform's ability to initiate HTTP requests to sensitive internal endpoints. 2. Access Controls: Restrict access to the SAP BI platform management interfaces and ensure that only authorized personnel can interact with the system. 3. Monitoring and Logging: Enable detailed logging and monitoring of outbound HTTP requests from the SAP platform to detect unusual or unauthorized request patterns indicative of SSRF attempts. 4. Patch Management: Although no patches are currently linked, maintain close communication with SAP for updates or security advisories and apply patches promptly once available. 5. Input Validation and Filtering: Where possible, configure or harden the SAP platform to validate and sanitize inputs that could be used to craft SSRF payloads. 6. Internal Endpoint Hardening: Secure internal HTTP endpoints by enforcing authentication, limiting exposure, and disabling unnecessary services to reduce the value of any enumerated information. 7. Incident Response Preparedness: Develop and test incident response plans that include detection and containment of SSRF exploitation attempts. 8. Vendor Engagement: Engage with SAP support to confirm if any configuration changes or mitigations can be applied immediately to reduce SSRF risk.

Description

Under certain conditions, SAP Business Objects Business Intelligence Platform allows an unauthenticated attacker to enumerate HTTP endpoints in the internal network by specially crafting HTTP requests. This disclosure of information could further enable the researcher to cause SSRF. It has no impact on integrity and availability of the application.

Impact

For European organizations using SAP Business Objects Business Intelligence Platform, this SSRF vulnerability could expose internal network endpoints to unauthenticated attackers, potentially revealing sensitive infrastructure details such as internal services, APIs, or management interfaces. While the vulnerability does not directly compromise data integrity or system availability, the disclosed information could facilitate lateral movement, privilege escalation, or targeted attacks within the internal network. Organizations in sectors with high reliance on SAP BI platforms, such as manufacturing, finance, and public administration, may face increased risk of internal reconnaissance by threat actors. Given the low CVSS score and high attack complexity, immediate catastrophic impact is unlikely; however, the vulnerability could serve as an initial foothold or information-gathering vector in multi-stage attacks. European organizations with complex internal networks and insufficient segmentation may be more vulnerable to follow-on exploitation. Additionally, compliance requirements under GDPR and other data protection regulations may be implicated if internal network information disclosure leads to further breaches or data exposure.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (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 10 Jul 2025, 23:49 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats