# CVE-2007-2149: Hardcoded credentials in n/a

> Attackers can read hardcoded credentials from source files or remote endpoints to gain unauthorized access and privileges in Chatness.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w2cx-3pp9-7qw4

## What is CVE-2007-2149?

CVE-2007-2149 is a critical vulnerability in n/a, published on 19 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stephen Craton (aka WiredPHP) Chatness 2.5.3 and earlier stores usernames and unencrypted passwords in (1) classes/vars.php and (2) classes/varstuff.php, and recommends 0666 or 0777 permissions for these files, which allows local users to gain privileges by reading the files, and allows remote attackers to obtain credentials via a direct request for admin/options.php.

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

It affects 1 product.


Products: Stephen Craton Chatness.

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

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

## Is CVE-2007-2149 being exploited?

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

Public exploit code:

- Chatness 2.5.3 - '/options.php/save.php' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2147](https://insights.sbomify.com/CVE-2007-2147/): Missing authorization in n/a (critical 10.0)
- [CVE-2007-2148](https://insights.sbomify.com/CVE-2007-2148/): Code injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2149 is a critical vulnerability in n/a, published on 19 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-2149 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-2149/ (Markdown: https://insights.sbomify.com/CVE-2007-2149/index.md)
```

## Sources

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

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