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

> Remote attackers can hijack administrator sessions to modify settings or add new admins via CSRF in Support Incident Tracker.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 29 Jan 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-r9jq-frx5-5cxf

## What is CVE-2011-5074?

CVE-2011-5074 is a medium-severity vulnerability in n/a, published on 29 Jan 2012. 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 request forgery (CSRF) vulnerabilities in Support Incident Tracker (aka SiT!) before 3.65 allow remote attackers to hijack the authentication of administrators for requests that change administrator email, add a new administrator, or insert arbitrary script via (1) user_profile_edit.php or (2) user_add.php.

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

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

It affects 1 product.


Products: Sitracker Support Incident Tracker.

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

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

## Is CVE-2011-5074 being exploited?

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

Public exploit code:

- sit! support incident tracker 3.64 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5635](https://insights.sbomify.com/CVE-2007-5635/): Multiple unspecified vulnerabilities in Salford Software Support Incident Tracker (SiT!) before 3.30 have unknown impact and attack vectors. (critical 10.0)
- [CVE-2011-3831](https://insights.sbomify.com/CVE-2011-3831/): SQL injection in n/a (high 7.5)
- [CVE-2011-4337](https://insights.sbomify.com/CVE-2011-4337/): Code injection in n/a (high 7.5)
- [CVE-2011-5071](https://insights.sbomify.com/CVE-2011-5071/): SQL injection in n/a (high 7.5)
- [CVE-2011-5072](https://insights.sbomify.com/CVE-2011-5072/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-5074 is a medium-severity vulnerability in n/a, published on 29 Jan 2012. 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-5074 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-5074/ (Markdown: https://insights.sbomify.com/CVE-2011-5074/index.md)
```

## Sources

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

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