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

> Authenticated attackers can inject scripts via Call ID in Cisco TelePresence web interface, enabling CSRF attacks that change passwords or cause denial of service.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/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:** 23 Sep 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x4c8-p6r9-9v52

## What is CVE-2011-2544?

CVE-2011-2544 is a low-severity cross-site scripting vulnerability in n/a, published on 23 Sep 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

Cross-site scripting (XSS) vulnerability in the web interface in Cisco TelePresence System MXP Series F9.1 and earlier allows remote authenticated users to inject arbitrary web script or HTML via a crafted Call ID, as demonstrated by resultant cross-site request forgery (CSRF) attacks that change passwords or cause a denial of service, aka Bug ID CSCtq46488.

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

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

It affects 3 products.


Products: Cisco Telepresence Mxp Software, Cisco Telepresence System 1000 Mxp, Cisco Telepresence System 1700 Mxp.

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

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

## Is CVE-2011-2544 being exploited?

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

Public exploit code:

- Cisco TelePresence SOS-11-010 - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2544 is a low-severity cross-site scripting vulnerability in n/a, published on 23 Sep 2011. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-2544 in the wild and no public exploit code.

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

## Sources

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

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