# CVE-2011-4005: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions via CSRF to execute arbitrary commands on Cisco Small Business routers.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 3 Nov 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m5hx-xvhh-69rp

## What is CVE-2011-4005?

CVE-2011-4005 is a critical vulnerability in n/a, published on 3 Nov 2011. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in the Services Ready Platform Configuration Utility web interface on the Cisco Small Business SRP521W, SRP526W, and SRP527W with firmware before 1.1.24 and the Small Business SRP541W, SRP546W, and SRP547W with firmware before 1.2.1 allows remote attackers to hijack the authentication of administrators for requests that execute arbitrary commands, aka Bug ID CSCtr45124.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 8 products.


Products: Cisco Small Business Srp520 Series Firmware, Cisco Small Business Srp521w, Cisco Small Business Srp526w, Cisco Small Business Srp527w, Cisco Small Business Srp540 Series Firmware, Cisco Small Business Srp541w, Cisco Small Business Srp546w, Cisco Small Business Srp547w.

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

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

## Is CVE-2011-4005 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-4005 is a critical vulnerability in n/a, published on 3 Nov 2011. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-4005 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-4005/ (Markdown: https://insights.sbomify.com/CVE-2011-4005/index.md)
```

## Sources

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

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