# CVE-2007-6618: JIRA Enterprise Edition before 3.12.1 allows remote attackers to delete another user's shared filter via a modified filter ID.


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-99xr-4v8h-g5x7

## What is CVE-2007-6618?

CVE-2007-6618 is a medium-severity vulnerability in Atlassian Jira, published on 3 Jan 2008. 

### Official description

JIRA Enterprise Edition before 3.12.1 allows remote attackers to delete another user's shared filter via a modified filter ID.

## Which versions are affected by CVE-2007-6618?

It affects 1 product.


Products: Atlassian Jira.

## How do I fix CVE-2007-6618?

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

## Is CVE-2007-6618 being exploited?

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

## Other vulnerabilities in Atlassian Jira

- [CVE-2020-14172](https://insights.sbomify.com/CVE-2020-14172/): Deserialization in Jira Server (critical 9.8)
- [CVE-2019-20409](https://insights.sbomify.com/CVE-2019-20409/): Code injection in Jira Server (critical 9.8)
- [CVE-2017-5983](https://insights.sbomify.com/CVE-2017-5983/): Deserialization in n/a (critical 9.8)
- [CVE-2010-1165](https://insights.sbomify.com/CVE-2010-1165/): Code injection in n/a (critical 9.0)
- [CVE-2016-4319](https://insights.sbomify.com/CVE-2016-4319/): Cross-site request forgery in Atlassian JIRA Server before 7.1.9 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6618 and fix it if it is affected.

What it is: CVE-2007-6618 is a medium-severity vulnerability in Atlassian Jira, published on 3 Jan 2008. 
Exploitation: There is no known exploitation of CVE-2007-6618 in the wild and no public exploit code.

Affected product: Atlassian Jira. 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-2007-6618/ (Markdown: https://insights.sbomify.com/CVE-2007-6618/index.md)
```

## Sources

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

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