# CVE-2008-6723: Auth bypass in n/a

> Remote attackers can bypass authentication and gain administrative access by manipulating the adminLogged cookie in TurnkeyForms Entertainment Portal.

- **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:** 14 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mr2r-xh4p-qmmp

## What is CVE-2008-6723?

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

### Official description

TurnkeyForms Entertainment Portal 2.0 allows remote attackers to bypass authentication and gain administrative access by setting the adminLogged cookie to Administrator.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Turnkeyforms Entertainment Portal.

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

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

## Is CVE-2008-6723 being exploited?

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

Public exploit code:

- TurnkeyForms Entertainment Portal 2.0 - Insecure Cookie Handling (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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