VulnerabilityPublished 8 Jul 2025

CVE-2025-31326: SAP BusinessObjects Business Intelligence Platform (Web Intelligence) · Basic XSS

Affects SAP BusinessObjects Business Intelligence Platform (Web Intelligence)Source CVE Database V5

Not known to be exploited · CVSS 4.1 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.1Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 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_SE SAP BusinessObjects Business Intelligence Platform (Web Intelligence)	Affected =2025 =2027	Fixed in–

AI-suggested

Implement strict input validation and output encoding on all user-controllable fields within the SAP BusinessObjects Web Intelligence platform to neutralize any HTML or script tags.
Apply the principle of least privilege by restricting user permissions to only those necessary for their roles, minimizing the number of users with access to vulnerable input fields.
Monitor and audit user inputs and report generation activities to detect any anomalous or suspicious behavior indicative of injection attempts.
Employ web application firewalls (WAF) with custom rules to detect and block HTML injection payloads targeting the BI platform.
Educate users about the risks of interacting with unexpected redirects or suspicious links within the BI reports.
Stay updated with SAP security advisories and apply patches or updates as soon as they become available.
Consider isolating the BI platform network segment and enforcing strict network segmentation to limit exposure.
Conduct regular security assessments and penetration testing focusing on input validation and injection vulnerabilities within the BI environment.

Description

SAP�BusinessObjects Business�Intelligence Platform (Web Intelligence) is vulnerable to HTML Injection, allowing an attacker with basic user privileges to inject malicious code into specific input fields. This could lead to unintended redirects or manipulation of application behavior, such as redirecting users to attacker-controlled domains. This issue primarily affects the integrity of the system. However, the confidentiality and availability of the system remain unaffected.

Impact

For European organizations using SAP BusinessObjects Business Intelligence Platform, this vulnerability poses a risk primarily to the integrity of their business intelligence data and application workflows. Attackers with basic user access could inject malicious HTML to manipulate reports or dashboards, potentially misleading users or redirecting them to phishing sites. While confidentiality and availability are not directly impacted, the integrity compromise could lead to erroneous business decisions based on manipulated data or loss of trust in the BI platform. This could be particularly damaging for sectors relying heavily on accurate BI data, such as finance, manufacturing, and public administration. Additionally, the redirection to attacker-controlled domains could facilitate further phishing or social engineering attacks targeting European employees. Given the widespread use of SAP products in Europe, especially in large enterprises and government entities, the vulnerability could be leveraged for targeted attacks aiming to disrupt business intelligence operations or conduct reconnaissance. The requirement for user interaction and low privilege reduces the likelihood of large-scale automated exploitation but does not eliminate risk in environments where many users have basic access.

CWE-80Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
Implementation
Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL…
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation
With Struts, write all data from form beans with the bean's filter attribute set to true.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.3.3 (opens in a new tab)
Attack patterns
XSS Targeting Non-Script Elements (opens in a new tab)
PHP Remote File Inclusion (opens in a new tab)
XSS Through HTTP Query Strings (opens in a new tab)
XSS Through HTTP Headers (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-80

Technical details

References

Community reviews

Related threats