# CVE-2011-4670: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in vTiger CRM, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Dec 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2w8x-37m4-26px

## What is CVE-2011-4670?

CVE-2011-4670 is a medium-severity cross-site scripting vulnerability in Vtiger Vtiger Crm, published on 2 Dec 2011. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in vTiger CRM 5.2.1 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) viewname parameter in a CalendarAjax action, (2) activity_mode parameter in a DetailView action, (3) contact_id and (4) parent_id parameters in an EditView action, (5) day, (6) month, (7) subtab, (8) view, and (9) viewOption parameters in the index action, and (10) start parameter in the ListView action to the Calendar module; (11) return_action and (12) return_module parameters in the EditView action, and (13) query parameter in an index action to the Campaigns module; (14) return_url and (15) workflow_id parameters in an editworkflow action to the com_vtiger_workflow module; (16) display_view parameter in an index action to the Dashboard module; (17) closingdate_end, (18) closingdate_start, (19) date_closed, (20) owner, (21) leadsource, (22) sales_stage, and (23) type parameters in a ListView action to the Potentials module; (24) folderid parameter in a SaveandRun action to the Reports module; (25) returnaction and (26) groupId parameters in a createnewgroup action, (27) mode and (28) parent parameters in a createrole action, (29) src_module in a ModuleManager action, (30) mode and (31) profile_id parameters in a profilePrivileges action, and (32) roleid parameter in a RoleDetailView to the Settings module; and (33) action parameter to the Home module and (34) module parameter to phprint.php.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2011-4670?

It affects 1 product.


Products: Vtiger Vtiger Crm.

## How do I fix CVE-2011-4670?

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

## Is CVE-2011-4670 being exploited?

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

Public exploit code:

- vTiger CRM 5.2.1 - 'index.php' Multiple Cross-Site Scripting Vulnerabilities (1) (exploitdb)
- vTiger CRM 5.2.1 - 'PHPrint.php' Multiple Cross-Site Scripting Vulnerabilities (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-2011-4670 and fix it if it is affected.

What it is: CVE-2011-4670 is a medium-severity cross-site scripting vulnerability in Vtiger Vtiger Crm, published on 2 Dec 2011. Any signed-in user can exploit it over the 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-2011-4670 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-2011-4670/ (Markdown: https://insights.sbomify.com/CVE-2011-4670/index.md)
```

## Sources

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

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