# CVE-2019-5009: File upload in n/a

> Attackers can upload malicious PHP files disguised as PNG images in the logo field to execute arbitrary code on the server.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xcm7-mpjr-9x9f

## What is CVE-2019-5009?

CVE-2019-5009 is a high-severity vulnerability in Vtiger Vtiger Crm, published on 4 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vtiger CRM 7.1.0 before Hotfix2 allows uploading files with the extension "php3" in the logo upload field, if the uploaded file is in PNG format and has a size of 150x40. One can put PHP code into the image; PHP code can be executed using "<? ?>" tags, as demonstrated by a CompanyDetailsSave action. This bypasses the bad-file-extensions protection mechanism. It is related to actions/CompanyDetailsSave.php, actions/UpdateCompanyLogo.php, and models/CompanyDetails.php.

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

## Which versions are affected by CVE-2019-5009?

It affects 1 product.


Products: Vtiger Vtiger Crm.

## How do I fix CVE-2019-5009?

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

## Is CVE-2019-5009 being exploited?

There is no known exploitation of CVE-2019-5009 in the wild and no public exploit code.

Public exploit code:

- Vtiger CRM 7.1.0 - Remote Code Execution (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-2019-5009 and fix it if it is affected.

What it is: CVE-2019-5009 is a high-severity vulnerability in Vtiger Vtiger Crm, published on 4 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5009 in the wild and no public exploit code.

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-2019-5009/ (Markdown: https://insights.sbomify.com/CVE-2019-5009/index.md)
```

## Sources

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

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