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

> Remote attackers can inject arbitrary web script via the pageTitle parameter in Axis M10 Series cameras, requiring admin access to exploit.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Feb 2013
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q4vq-55mw-v867

## What is CVE-2011-5261?

CVE-2011-5261 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Feb 2013. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in serverreport.cgi in Axis M10 Series Network Cameras M1054 firmware 5.21 and earlier allows remote attackers to inject arbitrary web script or HTML via the pageTitle parameter to admin/showReport.shtml.

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

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

It affects 2 products.


Products: Axis M1054 Network Camera, Axis M10 Series Network Cameras Firmware.

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

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

## Is CVE-2011-5261 being exploited?

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

Public exploit code:

- Axis M10 Series Network Cameras - Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-5261 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Feb 2013. An attacker needs administrator access to exploit it, 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-5261 exists.

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-5261/ (Markdown: https://insights.sbomify.com/CVE-2011-5261/index.md)
```

## Sources

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

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