Skip to content
Fencer Vulns
high 7.3

CVE-2016-1713 in the critical feed json

Unrestricted file upload vulnerability in the Settings_Vtiger_CompanyDetailsSave_Action class in modules/Settings/Vtiger/actions/CompanyDet…

published 2017-04-14 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-2808

cvss
7.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
16.6%
EPSS 16.6% chance of exploitation in 30 days, percentile 97%
public exploits
3
Metasploit, Exploit-DB

Summary

Unrestricted file upload vulnerability in the Settings_Vtiger_CompanyDetailsSave_Action class in modules/Settings/Vtiger/actions/CompanyDetailsSave.php in Vtiger CRM 6.4.0 allows remote authenticated users to execute arbitrary code by uploading a crafted image file with an executable extension, then accessing it via a direct request to the file in test/logo/. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-6000.

Timeline

  1. First public exploit (Metasploit exploit/multi/http/vtiger_logo_upload_exec)
  2. Published

Exploit prediction

16.56% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit exploit/multi/http/vtiger_logo_upload_exec Vtiger CRM - Authenticated Logo Upload RCE metasploit exploit, excellent rank, 2015-09-28
  • EDB-44379 Vtiger CRM 6.3.0 - (Authenticated) Arbitrary File Upload (Metasploit) webapps, 2018-03-30
  • EDB-38345 vTiger CRM 6.3.0 - (Authenticated) Remote Code Execution webapps, 2015-09-28
  • b.fl7.de http://b.fl7.de/2016/01/vtiger-crm-6.4-auth-rce.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type

References

Sources

Fencer Vulns 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.