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

Q: How do I fix CVE-2020-13134?

securechange: upgrade to r19-3. Exact commands for each OS are on this page.

Q: Is CVE-2020-13134 being exploited?

CVE-2020-13134 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-13134 affect?

CVE-2020-13134 affects securechange. Severity is medium (CVSS 4.8). 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) admin users. All TOS versions wi

Q: How urgent is CVE-2020-13134?

Priority 28/100. No elevated risk signals yet.

Routine

MEDIUM 4.8UPGRADE

CVE-2020-13134 is a medium-severity flaw (CVSS 4.8) affecting securechange. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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) admin 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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.5% (top 55%)
CISA exploited list	No
Weakness	CWE-79
Published	2021-01-20
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: tufin

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-01-20 02:15 UTCPublished CVE record published
2026-06-17 02:52 UTCUpdated Record last modified

tufin securechange UPGRADE

Affected: < r19-3 · r19-3 · r20-1

Fixed in: r19-3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy securechange || rpm -q securechange || securechange --version

2. UPGRADE to r19-3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade securechange

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade securechange

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-13134?

securechange: upgrade to r19-3. Exact commands for each OS are on this page.

Is CVE-2020-13134 being exploited?

CVE-2020-13134 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-13134 affect?

CVE-2020-13134 affects securechange. Severity is medium (CVSS 4.8). 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) admin users. All TOS versions wi

How urgent is CVE-2020-13134?

Priority 28/100. No elevated risk signals yet.

Related CVEs

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

References

← Back to latest CVEs