# CVE-2009-3249: Path traversal in n/a

> Remote attackers can execute arbitrary local files via directory traversal in vtiger CRM, potentially leading to full system compromise.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xjwx-qg8w-3x9p

## What is CVE-2009-3249?

CVE-2009-3249 is a high-severity path traversal vulnerability in Vtiger Vtiger Crm, published on 18 Sep 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in vtiger CRM 5.0.4 allow remote attackers to include and execute arbitrary local files via a .. (dot dot) in (1) the module parameter to graph.php; or the (2) module or (3) file parameter to include/Ajax/CommonAjax.php, reachable through modules/Campaigns/CampaignsAjax.php, modules/SalesOrder/SalesOrderAjax.php, modules/System/SystemAjax.php, modules/Products/ProductsAjax.php, modules/uploads/uploadsAjax.php, modules/Dashboard/DashboardAjax.php, modules/Potentials/PotentialsAjax.php, modules/Notes/NotesAjax.php, modules/Faq/FaqAjax.php, modules/Quotes/QuotesAjax.php, modules/Utilities/UtilitiesAjax.php, modules/Calendar/ActivityAjax.php, modules/Calendar/CalendarAjax.php, modules/PurchaseOrder/PurchaseOrderAjax.php, modules/HelpDesk/HelpDeskAjax.php, modules/Invoice/InvoiceAjax.php, modules/Accounts/AccountsAjax.php, modules/Reports/ReportsAjax.php, modules/Contacts/ContactsAjax.php, and modules/Portal/PortalAjax.php; and allow remote authenticated users to include and execute arbitrary local files via a .. (dot dot) in the step parameter in an Import action to the (4) Accounts, (5) Contacts, (6) HelpDesk, (7) Leads, (8) Potentials, (9) Products, or (10) Vendors module, reachable through index.php and related to modules/Import/index.php and multiple Import.php files.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2009-3249?

It affects 1 product.


Products: Vtiger Vtiger Crm.

## How do I fix CVE-2009-3249?

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

## Is CVE-2009-3249 being exploited?

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

Public exploit code:

- vTiger CRM 5.0.4 - Remote Code Execution / Cross-Site Request Forgery / Local File Inclusion / Cross-Site Scripting (exploitdb)
- vTiger CRM 5.0.4 - Local File Inclusion (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-2009-3249 and fix it if it is affected.

What it is: CVE-2009-3249 is a high-severity path traversal vulnerability in Vtiger Vtiger Crm, published on 18 Sep 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3249 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-2009-3249/ (Markdown: https://insights.sbomify.com/CVE-2009-3249/index.md)
```

## Sources

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

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