Skip to content
Fencer Intel
high 8.8

CVE-2019-14422 in the critical feed json

An issue was discovered in in TortoiseSVN 1.12.1.

published 7y ago modified 4mo ago also EUVD-2019-5625

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
16.4%
EPSS 16.4% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

An issue was discovered in in TortoiseSVN 1.12.1. The Tsvncmd: URI handler allows a customised diff operation on Excel workbooks, which could be used to open remote workbooks without protection from macro security settings to execute arbitrary code. A tsvncmd:command:diff?path:[file1]?path2:[file2] URI will execute a customised diff on [file1] and [file2] based on the file extension. For xls files, it will execute the script diff-xls.js using wscript, which will open the two files for analysis without any macro security warning. An attacker can exploit this by putting a macro virus in a network drive, and force the victim to open the workbooks and execute the macro inside.

Is CVE-2019-14422 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-47252)
  2. Published

Exploit prediction

16.39% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-47252 TortoiseSVN 1.12.1 - Remote Code Execution webapps, 2019-08-14
  • vulnerability-lab.com https://www.vulnerability-lab.com/get_content.php?id=2188 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2019/Aug/7 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.