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

> Remote attackers can bypass restrictions and obtain sensitive information by directly accessing specific PHP files in News Manager.

- **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:** 19 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fw58-883m-jp62

## What is CVE-2008-2343?

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

### Official description

News Manager 2.0 allows remote attackers to bypass restrictions and obtain sensitive information via a direct request to (1) db/connect_str.php and (2) login/info.php.

Weakness: CWE-264

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

It affects 1 product.


Products: News Manager News Manager.

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

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

## Is CVE-2008-2343 being exploited?

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

Public exploit code:

- newsmanager 2.0 - Remote File Inclusion / File Disclosure / SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-2340](https://insights.sbomify.com/CVE-2008-2340/): SQL injection in n/a (high 7.5)
- [CVE-2008-2342](https://insights.sbomify.com/CVE-2008-2342/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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