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

> Remote attackers can access administrative scripts without authentication, potentially reading or modifying sensitive data.

- **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:** 13 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vmq8-94rq-xchh

## What is CVE-2008-6718?

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

### Official description

U&M Software JustBookIt 1.0 does not require administrative authentication for all scripts in the admin/ directory, which allows remote attackers to have an unspecified impact via a direct request to (1) user_manual.php, (2) user_config.php, (3) user_kundnamn.php, (4) user_kundlista.php, (5) user_aktiva_kunder.php, (6) database.php, and possibly (7) index.php.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Uochm Justbookit.

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

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

## Is CVE-2008-6718 being exploited?

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

Public exploit code:

- U&M Software JustBookIt 1.0 - Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6718 is a high-severity missing authorization vulnerability in n/a, published on 13 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-6718 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-6718/ (Markdown: https://insights.sbomify.com/CVE-2008-6718/index.md)
```

## Sources

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

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