# CVE-2012-0303: Cross-site request forgery in n/a

> Remote attackers can hijack user sessions to execute commands or create admin accounts via CSRF in Symantec Message Filter.

- **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:** 5 Jul 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wjxw-8qch-jxmc

## What is CVE-2012-0303?

CVE-2012-0303 is a medium-severity vulnerability in n/a, published on 5 Jul 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 Brightmail Control Center in Symantec Message Filter 6.3 allow remote attackers to hijack the authentication of arbitrary users for requests that (1) execute application commands or (2) create admin accounts.

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

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

It affects 1 product.


Products: Symantec Message Filter.

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

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

## Is CVE-2012-0303 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0301](https://insights.sbomify.com/CVE-2012-0301/): Auth bypass in n/a (medium 5.4)
- [CVE-2012-0302](https://insights.sbomify.com/CVE-2012-0302/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-0300](https://insights.sbomify.com/CVE-2012-0300/): Information disclosure in n/a (low 3.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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