# CVE-2008-0440: Information disclosure in n/a

> Attackers can access user accounts because the forum software stores passwords in cleartext, exposing sensitive credentials.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xv44-cpqx-3w77

## What is CVE-2008-0440?

CVE-2008-0440 is a medium-severity vulnerability in n/a, published on 23 Jan 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AlstraSoft Forum Pay Per Post Exchange 2.0 stores passwords in cleartext, which makes it easier for attackers to access user accounts.

Weakness: CWE-255

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

It affects 1 product.


Products: Alstrasoft Forum Pay per Post Exchange.

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

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

## Is CVE-2008-0440 being exploited?

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

Public exploit code:

- Alstrasoft Forum Pay Per Post Exchange 2.0 - SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3954](https://insights.sbomify.com/CVE-2008-3954/): SQL injection in n/a (high 7.5)
- [CVE-2008-0429](https://insights.sbomify.com/CVE-2008-0429/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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