# CVE-2007-4047: Missing authorization in n/a

> Remote attackers can delete arbitrary comments and blogs in geoBlog due to missing authentication checks on admin scripts.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vr4m-cmfx-452h

## What is CVE-2007-4047?

CVE-2007-4047 is a medium-severity missing authorization vulnerability in n/a, published on 27 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

geoBlog (aka BitDamaged) 1 does not require authentication for (1) deletecomment.php, (2) deleteblog.php, and (3) listcomment.php in admin/, which allows remote attackers to delete arbitrary comments, delete arbitrary blogs, and have other unspecified impact via a request with a valid id parameter.

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

It affects 1 product.


Products: Geoblog Geoblog.

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

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

## Is CVE-2007-4047 being exploited?

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

Public exploit code:

- GeoBlog MOD_1.0 - 'deletecomment.php?id' Arbitrary Comment Deletion (exploitdb)
- GeoBlog MOD_1.0 - 'deleteblog.php?id' Arbitrary Blog Deletion (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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