# CVE-2008-7180: Missing authorization in n/a

> Remote attackers can delete arbitrary contacts in Telephone Directory 2008 by modifying the id parameter in a direct request.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vxw4-fmf5-g4wv

## What is CVE-2008-7180?

CVE-2008-7180 is a medium-severity missing authorization vulnerability in n/a, published on 8 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

del_query1.php in Telephone Directory 2008 allows remote attackers to delete arbitrary contacts via a direct request with a modified id variable.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Rittwick Banerjee Telephone Directory 2008.

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

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

## Is CVE-2008-7180 being exploited?

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

Public exploit code:

- Telephone Directory 2008 - Arbitrary Delete Contact (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7180 is a medium-severity missing authorization vulnerability in n/a, published on 8 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-7180 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-7180/ (Markdown: https://insights.sbomify.com/CVE-2008-7180/index.md)
```

## Sources

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

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