# CVE-2022-41266: Cross-site scripting in Commerce Webservices 2.0 (Swagger UI)

> Attackers can execute DOM XSS to steal tokens and achieve full account takeover in SAP Commerce Webservices.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/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:** 13 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-2jrj-r8hh-8g59

## What is CVE-2022-41266?

CVE-2022-41266 is a high-severity cross-site scripting vulnerability in SAP Commerce Webservices 2.0 (Swagger UI), published on 13 Dec 2022. 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 lack of proper input validation, SAP Commerce Webservices 2.0 (Swagger UI) - versions 1905, 2005, 2105, 2011, 2205, allows malicious inputs from untrusted sources, which can be leveraged by an attacker to execute a DOM Cross-Site Scripting (XSS) attack.  As a result, an attacker may be able to steal user tokens and achieve a full account takeover including access to administrative tools in SAP Commerce.

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

## Which versions are affected by CVE-2022-41266?

It affects 1 product.


Products: Sap Commerce Webservices 2.0.

## How do I fix CVE-2022-41266?

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

## Is CVE-2022-41266 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41266 and fix it if it is affected.

What it is: CVE-2022-41266 is a high-severity cross-site scripting vulnerability in SAP Commerce Webservices 2.0 (Swagger UI), published on 13 Dec 2022. 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-2022-41266 in the wild and no public exploit code.

Affected product: SAP Commerce Webservices 2.0 (Swagger UI). 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-2022-41266/ (Markdown: https://insights.sbomify.com/CVE-2022-41266/index.md)
```

## Sources

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

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