# CVE-2008-2276: Cross-site request forgery in n/a

> Remote attackers can create administrative users via CSRF in Mantis, requiring victim interaction to escalate privileges.

- **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:** 16 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-99j9-5php-mx3c

## What is CVE-2008-2276?

CVE-2008-2276 is a medium-severity vulnerability in n/a, published on 16 May 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in manage_user_create.php in Mantis 1.1.1 allows remote attackers to create new administrative users via a crafted link.

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

## Which versions are affected by CVE-2008-2276?

It affects 1 product.


Products: Matisbt Mantis.

## How do I fix CVE-2008-2276?

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

## Is CVE-2008-2276 being exploited?

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

Public exploit code:

- Mantis Bug Tracker 1.1.1 - Code Execution / Cross-Site Scripting / Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2276 and fix it if it is affected.

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

## Sources

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

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