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

> Remote attackers can inject arbitrary web script or HTML via various input fields in iTop, potentially compromising user sessions and data.

- **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:** 26 Nov 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h57m-vxj9-8gpv

## What is CVE-2011-4275?

CVE-2011-4275 is a medium-severity cross-site scripting vulnerability in Combodo Itop, published on 26 Nov 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 iTop (aka IT Operations Portal) 1.1.181 and 1.2.0-RC-282 allow remote attackers to inject arbitrary web script or HTML via (1) a crafted company name, (2) a crafted database server name, (3) a crafted CSV file, (4) a crafted copy-and-paste action, (5) the auth_user parameter in a suggest_pwd action to UI.php, (6) the c[menu] parameter to UniversalSearch.php, (7) the description parameter in a SearchFormToAdd_document_list action to UI.php, (8) the category parameter in an errors action to audit.php, or (9) the suggest_pwd parameter to UI.php.

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

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

It affects 1 product.


Products: Combodo Itop.

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

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

## Is CVE-2011-4275 being exploited?

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

Public exploit code:

- Piwik Open Flash Chart - Remote Code Execution (exploitdb)
- OpenEMR 4.1.1 - 'ofc_upload_image.php' Arbitrary File Upload (exploitdb)
- OpenEMR - Arbitrary '.PHP' File Upload (Metasploit) (exploitdb)
- Joomla! Component com_civicrm 4.2.2 - Remote Code Injection (exploitdb)
- ZonPHP 2.25 - Remote Code Execution (exploitdb)
- Open Flash Chart 2 - Arbitrary File Upload (Metasploit) (exploitdb)

## Other vulnerabilities in Combodo Itop

- [CVE-2023-48710](https://insights.sbomify.com/CVE-2023-48710/): iTop limit pages/exec.php script to PHP files (critical 9.8)
- [CVE-2022-39214](https://insights.sbomify.com/CVE-2022-39214/): Authenticated users of Combodo iTop can take over any account (critical 9.6)
- [CVE-2021-41161](https://insights.sbomify.com/CVE-2021-41161/): XSS in csvimport in 3.0.0-beta versions (critical 9.3)
- [CVE-2021-41162](https://insights.sbomify.com/CVE-2021-41162/): Cross-site Scripting in Combodo iTop (critical 9.3)
- [CVE-2025-47773](https://insights.sbomify.com/CVE-2025-47773/): Combodo iTop has XSS vulnerability in /pages/ajax.render.php (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4275 and fix it if it is affected.

What it is: CVE-2011-4275 is a medium-severity cross-site scripting vulnerability in Combodo Itop, published on 26 Nov 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-4275 exists.

Affected product: Combodo Itop. 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-4275/ (Markdown: https://insights.sbomify.com/CVE-2011-4275/index.md)
```

## Sources

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

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