# CVE-2008-1507: Hardcoded credentials in n/a

> Default administrative accounts with known passwords allow remote attackers to gain full administrative access to the PEEL CMS.

- **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:** 25 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xqc3-f6fp-p8x7

## What is CVE-2008-1507?

CVE-2008-1507 is a high-severity vulnerability in n/a, published on 25 Mar 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PEEL, possibly 3.x and earlier, has (1) a default info@peel.fr account with password admin, and (2) a default contact@peel.fr account with password cinema, which allows remote attackers to gain administrative access.

Weakness: CWE-16

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

It affects 1 product.


Products: Peel Peel.

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

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

## Is CVE-2008-1507 being exploited?

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

Public exploit code:

- PEEL CMS 3.x - Admin Hash Extraction / Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6892](https://insights.sbomify.com/CVE-2008-6892/): SQL injection in n/a (high 7.5)
- [CVE-2008-1496](https://insights.sbomify.com/CVE-2008-1496/): SQL injection in n/a (high 7.5)
- [CVE-2005-3572](https://insights.sbomify.com/CVE-2005-3572/): SQL injection in n/a (high 7.5)
- [CVE-2008-1495](https://insights.sbomify.com/CVE-2008-1495/): File upload in n/a (medium 6.5)
- [CVE-2008-1506](https://insights.sbomify.com/CVE-2008-1506/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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