# CVE-2025-42920: Cross-Site Scripting (XSS) vulnerability in SAP Supplier Relationship Management

> An unauthenticated attacker can execute malicious scripts in a victim's browser via a crafted link, allowing access to and modification of victim data.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 9 Sep 2025
- **Also known as:** GHSA-x2fx-g3ch-j487

## What is CVE-2025-42920?

CVE-2025-42920 is a medium-severity cross-site scripting vulnerability in SAP_SE SAP Supplier Relationship Management, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Due to a Cross-Site Scripting (XSS) vulnerability in the SAP Supplier Relationship Management, an unauthenticated attacker could generate a malicious link and make it publicly accessible. If an authenticated victim clicks on the link, the injected input is processed during the page generation, resulting in the execution of malicious content. This execution allows the attacker to access and modify information within the victim's browser scope, impacting confidentiality and integrity, while availability remains unaffected.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-42920?

It affects 1 product.


Products: Sap Supplier Relationship Management.

## How do I fix CVE-2025-42920?

No fix has been published for CVE-2025-42920 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-42920 being exploited?

There is no known exploitation of CVE-2025-42920 in the wild and no public exploit code.

## Other vulnerabilities in SAP_SE SAP Supplier Relationship Management

- [CVE-2025-30012](https://insights.sbomify.com/CVE-2025-30012/): Multiple vulnerabilities in SAP Supplier Relationship Management (Live Auction Cockpit) (critical 10.0)
- [CVE-2025-30018](https://insights.sbomify.com/CVE-2025-30018/): Multiple vulnerabilities in SAP Supplier Relationship Management (Live Auction Cockpit) (high 8.6)
- [CVE-2025-30009](https://insights.sbomify.com/CVE-2025-30009/): Multiple vulnerabilities in SAP Supplier Relationship Management (Live Auction Cockpit) (medium 6.1)
- [CVE-2025-30010](https://insights.sbomify.com/CVE-2025-30010/): Multiple vulnerabilities in SAP Supplier Relationship Management (Live Auction Cockpit) (medium 6.1)
- [CVE-2019-0361](https://insights.sbomify.com/CVE-2019-0361/): Cross-site scripting in SAP Supplier Relationship Management (Master Data Management Catalog) (SRM MDM CAT) (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-42920 and fix it if it is affected.

What it is: CVE-2025-42920 is a medium-severity cross-site scripting vulnerability in SAP_SE SAP Supplier Relationship Management, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-42920 in the wild and no public exploit code.

Affected product: SAP_SE SAP Supplier Relationship Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-42920/ (Markdown: https://insights.sbomify.com/CVE-2025-42920/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-42920
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-42920
- OSV: https://osv.dev/vulnerability/CVE-2025-42920

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-42920/
Summaries are generated and may contain mistakes; the official description above is the record.