Skip to main content
VulnerabilityPublished Updated

CVE-2025-27434: SAP Commerce (Swagger UI) · Cross-site Scripting

Affects SAP Commerce (Swagger UI)Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

AI-suggested

To mitigate CVE-2025-27434 effectively, organizations should implement the following specific measures: 1) Restrict access to the Swagger UI interface by limiting it to trusted internal networks or VPNs, thereby reducing exposure to unauthenticated external attackers. 2) Deploy web application firewalls (WAFs) with robust XSS detection and prevention rules tailored to SAP Commerce traffic patterns to block malicious payloads before they reach the application. 3) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts within the Swagger UI context. 4) Monitor logs and network traffic for unusual requests targeting the Swagger UI endpoints, enabling early detection of exploitation attempts. 5) Engage with SAP support channels to obtain patches or official guidance as soon as they become available and apply updates promptly. 6) Educate internal users about the risks of interacting with untrusted Swagger UI instances and encourage cautious behavior regarding unexpected prompts or inputs. 7) Consider disabling or limiting Swagger UI in production environments if not strictly necessary, or replacing it with more secure API documentation tools. These targeted actions go beyond generic advice and address the specific attack vectors and exposure scenarios of this vulnerability.

Description

Due to insufficient input validation, SAP Commerce (Swagger UI) allows an unauthenticated attacker to inject the malicious code from remote sources, which can be leveraged by an attacker to execute a cross-site scripting (XSS) attack. This could lead to a high impact on the confidentiality, integrity, and availability of data in SAP Commerce.

References

Community reviews

Loading reviews…