# CVE-2007-2081: Auth bypass in n/a

> Remote attackers can bypass authentication in MyBlog by manipulating the admin cookie, gaining unauthorized access to administrative functions.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/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:** 18 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gw3f-6rqc-fm2w

## What is CVE-2007-2081?

CVE-2007-2081 is a high-severity authentication bypass vulnerability in n/a, published on 18 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MyBlog 0.9.8 and earlier allows remote attackers to bypass authentication requirements via the admin cookie parameter to certain admin files, as demonstrated by admin/settings.php.

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

It affects 1 product.


Products: Myblog Myblog.

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

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

## Is CVE-2007-2081 being exploited?

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

Public exploit code:

- MyBlog 0.9.8 - 'Settings.php' Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-4341](https://insights.sbomify.com/CVE-2008-4341/): Auth bypass in n/a (high 7.5)
- [CVE-2008-2963](https://insights.sbomify.com/CVE-2008-2963/): SQL injection in n/a (medium 6.8)
- [CVE-2007-2082](https://insights.sbomify.com/CVE-2007-2082/): Code injection in n/a (medium 6.5)
- [CVE-2008-6193](https://insights.sbomify.com/CVE-2008-6193/): Information disclosure in n/a (medium 5.0)
- [CVE-2008-2962](https://insights.sbomify.com/CVE-2008-2962/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2081 is a high-severity authentication bypass vulnerability in n/a, published on 18 Apr 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-2081 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-2081/ (Markdown: https://insights.sbomify.com/CVE-2007-2081/index.md)
```

## Sources

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

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