# CVE-2016-1713: File upload in n/a

> Authenticated attackers can upload malicious files to Vtiger CRM to execute arbitrary code on the server.

- **Severity:** High 7.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h8jm-h3mr-79gp

## What is CVE-2016-1713?

CVE-2016-1713 is a high-severity vulnerability in Vtiger Vtiger Crm, published on 14 Apr 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2016-1713?

It affects 1 product.


Products: Vtiger Vtiger Crm.

## How do I fix CVE-2016-1713?

No fix has been published for CVE-2016-1713 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-1713 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-1713 exists.

Public exploit code:

- vTiger CRM 6.3.0 - (Authenticated) Remote Code Execution (exploitdb)
- Vtiger CRM - Authenticated Logo Upload RCE (metasploit)
- Vtiger CRM 6.3.0 - (Authenticated) Arbitrary File Upload (Metasploit) (exploitdb)

## Other vulnerabilities in Vtiger Vtiger Crm

- [CVE-2020-22807](https://insights.sbomify.com/CVE-2020-22807/): SQL injection in n/a (critical 9.8)
- [CVE-2013-3215](https://insights.sbomify.com/CVE-2013-3215/): Auth bypass in n/a (critical 9.8)
- [CVE-2013-3214](https://insights.sbomify.com/CVE-2013-3214/): Code injection in n/a (critical 9.8)
- [CVE-2009-3250](https://insights.sbomify.com/CVE-2009-3250/): File upload in n/a (critical 9.0)
- [CVE-2009-3258](https://insights.sbomify.com/CVE-2009-3258/): Missing authorization in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1713 and fix it if it is affected.

What it is: CVE-2016-1713 is a high-severity vulnerability in Vtiger Vtiger Crm, published on 14 Apr 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-1713 exists.

Affected product: Vtiger Vtiger Crm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-1713/ (Markdown: https://insights.sbomify.com/CVE-2016-1713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-1713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-1713
- OSV: https://osv.dev/vulnerability/CVE-2016-1713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-1713/
Summaries are generated and may contain mistakes; the official description above is the record.