# CVE-2012-4730: Other in n/a

> Authenticated users can inject email headers to conduct phishing attacks or leak sensitive information in Request Tracker.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/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:** Yes
- **Published:** 11 Nov 2012
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2012-4730, GHSA-53rc-933r-8227

## What is CVE-2012-4730?

CVE-2012-4730 is a low-severity vulnerability in n/a, published on 11 Nov 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

Request Tracker (RT) 3.8.x before 3.8.15 and 4.0.x before 4.0.8 allows remote authenticated users with ModifySelf or AdminUser privileges to inject arbitrary email headers and conduct phishing attacks or obtain sensitive information via unknown vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2012-4730?

It affects 1 product.


Products: Bestpractical Rt.

## How do I fix CVE-2012-4730?

Upgrade to a fixed version.

## Is CVE-2012-4730 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-5092](https://insights.sbomify.com/CVE-2011-5092/): Privilege escalation in n/a (high 7.5)
- [CVE-2013-3370](https://insights.sbomify.com/CVE-2013-3370/): Missing authorization in n/a (medium 6.8)
- [CVE-2012-4732](https://insights.sbomify.com/CVE-2012-4732/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2011-2085](https://insights.sbomify.com/CVE-2011-2085/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2011-4458](https://insights.sbomify.com/CVE-2011-4458/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4730 and fix it if it is affected.

What it is: CVE-2012-4730 is a low-severity vulnerability in n/a, published on 11 Nov 2012. 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-2012-4730 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-2012-4730/ (Markdown: https://insights.sbomify.com/CVE-2012-4730/index.md)
```

## Sources

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

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