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

> Remote attackers can inject arbitrary web script or HTML into Mutare EVM via delivery address or PIN fields, requiring user interaction.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f6g3-fh8w-f8x8

## What is CVE-2011-1105?

CVE-2011-1105 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 2011. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Mutare EVM allow remote attackers to inject arbitrary web script or HTML via (1) a delivery address and possibly (2) a PIN.

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

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

It affects 1 product.


Products: Mutare Evm.

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

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

## Is CVE-2011-1105 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1104](https://insights.sbomify.com/CVE-2011-1104/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1105 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 2011. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-1105 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-1105/ (Markdown: https://insights.sbomify.com/CVE-2011-1105/index.md)
```

## Sources

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

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